APRS Packet Errors for S56DS-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
20260209092632S56DS-10>APLRG1,TCPIP*,qAC,T2RADOM:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209095333S56DS-10>APLRG1,TCPIP*,qAC,T2RADOM:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209102033S56DS-10>APLRG1,TCPIP*,qAC,T2RADOM:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209104733S56DS-10>APLRG1,TCPIP*,qAC,T2RADOM:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209111433S56DS-10>APLRG1,TCPIP*,qAC,T2RADOM:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209114133S56DS-10>APLRG1,TCPIP*,qAC,T2RADOM:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209120833S56DS-10>APLRG1,TCPIP*,qAC,T2RADOM:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209121732S56DS-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209124432S56DS-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209131132S56DS-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209133832S56DS-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209140532S56DS-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209143232S56DS-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L7>jgR(R{a GLoRa APRS - iGate Strmca
20260209145932S56DS-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L7>jgR(R{a GLoRa APRS - iGate Strmca