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
20260208144609	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208151624	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208154639	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208161657	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208164712	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208171727	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208174742	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208181801	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208184816	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208191831	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208194846	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273
20260208201904	DL2KI-5>APRSGW,TCPIP*,qAR,DL2KI-5:!5045.50N/00751.13E##MeshCom, T-Beam/B=079/A=001273