APRS Packet Errors for N0OQA (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
20260209140957N0OQA>APK102,2-2,qAR,K0VSC-1:=4520.72N/09335.52W_195/005g007t029r p P000h85b10152KU2k
20260209144459N0OQA>APK102,2-2,qAR,N0NQD-1:=4520.72N/09335.52W_197/005g007t030r p P000h84b10152KU2k
20260209161507N0OQA>APK102,2-2,qAR,N0NQD-1:=4520.72N/09335.52W_172/004g006t033r p P000h81b10143KU2k
20260209182516N0OQA>APK102,2-2,qAR,K0VSC-1:=4520.72N/09335.52W_207/006g007t036r p P000h75b10097KU2k
20260209185518N0OQA>APK102,2-2,qAR,N0ANC-2:=4520.72N/09335.52W_200/006g009t036r p P000h75b10122KU2k
20260209190019N0OQA>APK102,2-2,qAR,N0NQD-1:=4520.72N/09335.52W_193/004g005t037r p P000h76b10119KU2k