APRS Packet Errors for DL2KI-5 (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
20260209092555	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209095610	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209102629	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209105644	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209112659	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209115714	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209122733	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209125748	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209132801	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209135816	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260209142831	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273