APRS Packet Errors for DG8NFO-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
20260208152257	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0BT-20:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906
20260208162314	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0NH-3:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906
20260208165326	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0NH-3:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906
20260208172341	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0NH-3:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906
20260208175359	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0NH-3:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906
20260208182423	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0NH-3:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906
20260208185429	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0NH-3:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906
20260208192459	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0NH-3:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906
20260208202525	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0NH-3:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906
20260208205532	DG8NFO-12>APRSMC,TCPIP*,qAR,DB0NH-3:!5005.89N/01048.07E#MeshCom Ebern/BY#Oliver/B=100/A=000906