APRS Packet Errors for SP4BG (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
20261014170002SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>FM SVXLink Node
20261014170003SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>PHG1010
20261014172002SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>FM SVXLink Node
20261014172003SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>PHG1010
20261014174001SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>FM SVXLink Node
20261014174002SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>PHG1010
20261014181001SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>FM SVXLink Node
20261014181002SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>PHG1010
20261014183001SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>FM SVXLink Node
20261014183002SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>PHG1010
20261014185002SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>FM SVXLink Node
20261014185003SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>PHG1010
20261014192002SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>FM SVXLink Node
20261014192003SP4BG>APSVX1,TCPIP*,qAC,T2POLAND:=53.58.26N/020.32.52E>PHG1010