APRS Packet Errors for 2M1GPR-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
202602091550052M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater
202602091620052M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater
202602091650052M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater
202602091720052M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater
202602091750052M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater
202602091820052M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater
202602091850052M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater
202602091920052M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater
202602091950052M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater
202602092120062M1GPR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L1=9XM$Nra GLoRa APRS iGate/digipeater