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
20260208145430n3uvr>APN000,TCPIP*,qAC,T2SYDNEY:@081423z4129.47N/07533.81W_178/000g000t006r000p000P000b10223h67L410eMB62
20260208155454n3uvr>APN000,TCPIP*,qAC,T2CSNGRAD:@081523z4129.47N/07533.81W_308/000g000t008r000p000P000b10223h60L454eMB62
20260208164428n3uvr>APN000,TCPIP*,qAC,T2LAUSITZ:@081613z4129.47N/07533.81W_149/000g000t011r000p000P000b10225h55L510eMB62