APRS Packet Errors for DL2GKH-16 (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
20260209091852	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=100/A=001421
20260209094907	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=088/A=001421
20260209104937	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=100/A=001421
20260209111952	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=100/A=001421
20260209115007	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=100/A=001421
20260209122022	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=100/A=001421
20260209125037	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=100/A=001421
20260209132054	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=100/A=001421
20260209135107	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=100/A=001421
20260209142122	DL2GKH-16>APRSMC,TCPIP*,qAR,DB0HRH-12:!4735.65N/00822.01ErMeshCom 4.0#Hermann/B=100/A=001421