APRS Packet Errors for SP6EU (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
20251026225001SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nFM SVXLink Node
20251026225002SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nPHG1010
20251026231002SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nFM SVXLink Node
20251026231003SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nPHG1010
20251026234001SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nFM SVXLink Node
20251026234002SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nPHG1010
20251027000001SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nFM SVXLink Node
20251027000002SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nPHG1010
20251027002002SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nFM SVXLink Node
20251027002003SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nPHG1010
20251027005001SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nFM SVXLink Node
20251027005002SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nPHG1010
20251027011002SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nFM SVXLink Node
20251027011003SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nPHG1010
20251027013002SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nFM SVXLink Node
20251027013003SP6EU>APSVX1,TCPIP*,qAC,T2POLAND:=5112.22N/016.1584nPHG1010