APRS Packet Errors for SP2JAR-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
20260321094029	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnFM SVXLink Node
20260321094030	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnPHG1010
20260321100001	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnFM SVXLink Node
20260321100002	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnPHG1010
20260321102001	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnFM SVXLink Node
20260321102002	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnPHG1010
20260321105002	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnFM SVXLink Node
20260321105003	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnPHG1010
20260321111002	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnFM SVXLink Node
20260321111003	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnPHG1010
20260321113001	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnFM SVXLink Node
20260321113002	SP2JAR-10>APSVX1,TCPIP*,qAC,T2POLAND:=53.108701N/18.000076EnPHG1010