APRS Packet Errors for OE3AJC-12 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20260208165756OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XER-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208172807OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XER-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208182839OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XER-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208185903OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XER-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208191204OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XER-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208192909OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XER-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208202956OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XWJ-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208205954OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XER-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208213014OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XWJ-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208220025OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XER-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539
20260208223039OE3AJC-12>APRSMC,TCPIP*,qAR,OE3XER-12:!4853.48N/01518.75E#via MeshCom; QRV#lerry/A=001539