APRS Packet Errors for DL0RN-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
20260209091304DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209092805DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209094305DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209095806DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209101306DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209102806DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209104307DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209105807DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209111308DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209112809DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209114309DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209115810DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209121310DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209122810DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209124310DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209125811DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209131311DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209132811DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209134312DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209135812DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209141313DL0RN-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209142813DL0RN-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209144314DL0RN-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM
20260209145814DL0RN-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L4O>nP2:.& xGLoRa-APRS DARC-OV Rheinhausen L20, 145.375 FM