APRS Packet Errors for n3uvr (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
20260209105818n3uvr>APN000,TCPIP*,qAC,T2ERFURT:@091026z4129.47N/07533.81W_127/000g000t002r000p000P000b10255h82L000eMB62
20260209120835n3uvr>APN000,TCPIP*,qAC,T2ROMANIA:@091136z4129.47N/07533.81W_127/000g000t004r000p000P000b10257h81L000eMB62
20260209125858n3uvr>APN000,TCPIP*,qAC,T2ROMANIA:@091226z4129.47N/07533.81W_127/000g000t004r000p000P000b10257h82L007eMB62
20260209141832n3uvr>APN000,TCPIP*,qAC,T2PERTH:@091346z4129.47N/07533.81W_127/000g000t007r000p000P000b10260h77L081eMB62