APRS Packet Errors for DN9HC-98 (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
20260209160024DN9HC-98>APRSMC,TCPIP*,qAR,DM2HEY-99:!5121.53N/01050.26E#MeshCom-Thuerin#Marcel/B=100/A=000922
20260209163036DN9HC-98>APRSMC,TCPIP*,qAR,DM2HEY-99:!5121.53N/01050.26E#MeshCom-Thuerin#Marcel/B=100/A=000922
20260209173109DN9HC-98>APRSMC,TCPIP*,qAR,DM2HEY-99:!5121.53N/01050.26E#MeshCom-Thuerin#Marcel/B=100/A=000922
20260209180124DN9HC-98>APRSMC,TCPIP*,qAR,DM2HEY-99:!5121.53N/01050.26E#MeshCom-Thuerin#Marcel/B=100/A=000922
20260209190155DN9HC-98>APRSMC,TCPIP*,qAR,DM2HEY-99:!5121.53N/01050.26E#MeshCom-Thuerin#Marcel/B=100/A=000922
20260209193210DN9HC-98>APRSMC,TCPIP*,qAR,DM2HEY-99:!5121.53N/01050.26E#MeshCom-Thuerin#Marcel/B=100/A=000922
20260209203240DN9HC-98>APRSMC,TCPIP*,qAR,DM2HEY-99:!5121.53N/01050.26E#MeshCom-Thuerin#Marcel/B=100/A=000922
20260209210255DN9HC-98>APRSMC,TCPIP*,qAR,DM2HEY-99:!5121.53N/01050.26E#MeshCom-Thuerin#Marcel/B=100/A=000922