APRS Packet Errors for OZ9DIO-20 (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
20260208181217OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208184218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208191218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208194218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208201218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208204218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208211218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208214218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208221218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208224218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208231218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD
20260208234218OZ9DIO-20>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2KulQD0(a GLoRa APRS Slagelse - OZ1ANE-OZ5BD