APRS Packet Errors for DG4LD-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
20260209131608DG4LD-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209141638DG4LD-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209144658DG4LD-12>APRSMC,TCPIP*,qAR,DB0SH-1:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209151716DG4LD-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209154727DG4LD-12>APRSMC,TCPIP*,qAR,DB0SH-1:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209161743DG4LD-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209164800DG4LD-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209171815DG4LD-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209174840DG4LD-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209181845DG4LD-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085
20260209184911DG4LD-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5448.72N/00923.92E#MeshCom#DG4LD-12/B=100/A=000085