APRS Packet Errors for SP4SR-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
20260209092046	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209095058	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209102113	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209105128	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209112144	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209115159	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209122214	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209125229	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209132248	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209135306	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209142315	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554
20260209145330	SP4SR-10>APRSGW,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E&MeshCom IGate#Slawomir/A=000554