APRS Packet Errors for SR9VJK-12 (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
20260209094242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209101242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209104242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209111242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209114242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209121242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209124242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209131242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209134242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209141242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209144242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz
20260209151242	SR9VJK-12>APLOX1,TCPIP*,qAC,T2CSNGRAD:!4925.05NL02053.71E#LoRa iGate 434.855MHz