APRS Packet Errors for SP9RQA (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
20260208145437SP9RQA>APRS,TCPIP*,qAC,FIFTH:=4938.68N/02106.04E_.../...g...t036r...p...P...h78b10044
20260208152438SP9RQA>APRS,TCPIP*,qAC,SIXTH:=4938.68N/02106.04E_.../...g...t035r...p...P...h78b10045
20260208155441SP9RQA>APRS,TCPIP*,qAC,SECOND:=4938.68N/02106.04E_.../...g...t035r...p...P...h79b10048
20260208162437SP9RQA>APRS,TCPIP*,qAC,NINTH:=4938.68N/02106.04E_.../...g...t035r...p...P...h79b10050
20260208165437SP9RQA>APRS,TCPIP*,qAC,SEVENTH:=4938.68N/02106.04E_.../...g...t034r...p...P...h80b10054
20260208172437SP9RQA>APRS,TCPIP*,qAC,SIXTH:=4938.68N/02106.04E_.../...g...t034r...p...P...h80b10057
20260208175437SP9RQA>APRS,TCPIP*,qAC,FIFTH:=4938.68N/02106.04E_.../...g...t034r...p...P...h80b10059
20260208182437SP9RQA>APRS,TCPIP*,qAC,FIFTH:=4938.68N/02106.04E_.../...g...t034r...p...P...h81b10062
20260208185437SP9RQA>APRS,TCPIP*,qAC,THIRD:=4938.68N/02106.04E_.../...g...t034r...p...P...h81b10065
20260208192437SP9RQA>APRS,TCPIP*,qAC,NINTH:=4938.68N/02106.04E_.../...g...t034r...p...P...h82b10067
20260208195437SP9RQA>APRS,TCPIP*,qAC,FOURTH:=4938.68N/02106.04E_.../...g...t033r...p...P...h82b10069
20260208202447SP9RQA>APRS,TCPIP*,qAC,SECOND:=4938.68N/02106.04E_.../...g...t033r...p...P...h82b10071