APRS Packet Errors for DO3NOW-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
20260208145634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208152634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208155634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208162634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208165634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208172634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208175634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208182634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208185634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208192634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208195634	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=100/A=001280
20260208202635	DO3NOW-12>APRSGW,TCPIP*,qAR,DO3NOW-12:!4845.75N/01214.26EGMeshcom Gateway/B=093/A=001280