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
20251215161002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rFM SVXLink Node
20251215161003SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rPHG1010
20251215163001SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rFM SVXLink Node
20251215163002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rPHG1010
20251215165002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rFM SVXLink Node
20251215165003SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rPHG1010
20251215172001SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rFM SVXLink Node
20251215172002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rPHG1010
20251215174002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rFM SVXLink Node
20251215174003SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rPHG1010
20251215180001SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rFM SVXLink Node
20251215180002SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rPHG1010
20251215183001SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rFM SVXLink Node
20251215183003SP6DWA-FM>APSVX1,TCPIP*,qAC,T2POLAND:=50.48466/17.34167rPHG1010