APRS Packet Errors for DB0GER-99 (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
20260208150213DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033
20260208160240DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033
20260208163255DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033
20260208173325DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033
20260208180340DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033
20260208183355DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033
20260208190410DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033
20260208193428DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033
20260208200440DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033
20260208203455DB0GER-99>APRSMC,TCPIP*,qAR,DL6UM-12:!5052.87NM01207.73E#test#db0ger-99/B=100/A=001033