APRS Packet Errors for SP6DWA-FM (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
20251125134001SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nFM SVXLink Node
20251125134002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nPHG1010
20251125145002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nFM SVXLink Node
20251125145003SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nPHG1010
20251125151001SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nFM SVXLink Node
20251125151002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nPHG1010
20251125153002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nFM SVXLink Node
20251125153003SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nPHG1010
20251125160001SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nFM SVXLink Node
20251125160002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nPHG1010
20251125162002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nFM SVXLink Node
20251125162003SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nPHG1010
20251125164001SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nFM SVXLink Node
20251125164003SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=5029.08N/17.2051nPHG1010