APRS Packet Errors for DB0EZ (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
20260208151702	DB0EZ>APRS,qAC,DB0ED:!4818.10N/01154.87Er70cm FM-Relais Erding/Stadt 439.1625 -7,6 t-ctcss 77Hz, Relaiscluster Lkr. Erding
20260208161702	DB0EZ>APRS,qAC,DB0ED:!4818.10N/01154.87Er70cm FM-Relais Erding/Stadt 439.1625 -7,6 t-ctcss 77Hz, Relaiscluster Lkr. Erding
20260208171702	DB0EZ>APRS,qAC,DB0ED:!4818.10N/01154.87Er70cm FM-Relais Erding/Stadt 439.1625 -7,6 t-ctcss 77Hz, Relaiscluster Lkr. Erding
20260208181702	DB0EZ>APRS,qAC,DB0ED:!4818.10N/01154.87Er70cm FM-Relais Erding/Stadt 439.1625 -7,6 t-ctcss 77Hz, Relaiscluster Lkr. Erding
20260208191702	DB0EZ>APRS,qAC,DB0ED:!4818.10N/01154.87Er70cm FM-Relais Erding/Stadt 439.1625 -7,6 t-ctcss 77Hz, Relaiscluster Lkr. Erding
20260208201701	DB0EZ>APRS,qAC,DB0ED:!4818.10N/01154.87Er70cm FM-Relais Erding/Stadt 439.1625 -7,6 t-ctcss 77Hz, Relaiscluster Lkr. Erding