APRS Packet Errors for SP2JP-10 (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
20260208132901SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208135901SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208142901SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208145901SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208152900SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208155901SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208162901SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208165901SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208172901SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208175900SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208182901SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855
20260208185900SP2JP-10>APWW11,TCPIP*,qAC,SP2PUT:=5306.79NL01759.19E#LoRa APRS iGate&Digi @1k2 434.855