APRS Packet Errors for DJ5CM-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
20260208134213	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208141228	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208144247	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208151311	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0HEI-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208152848	DJ5CM-12>APRSGW,TCPIP*,qAR,DJ5CM-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208153143	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0HEI-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208155238	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208163300	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0HEI-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208170315	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0HEI-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208180345	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0HEI-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208183404	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075
20260208190415	DJ5CM-12>APRSMC,TCPIP*,qAR,DB0HEI-12:!5427.17N/00934.10E&MeshCom M13/B=100/A=000075