APRS Packet Errors for OE4DNS-2 (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
20260209092559OE4DNS-2>APLRG1,WIDE1-1,qAO,HA1KHJ-10:!L6:HMRg(^a GLoRa_APRS_iGate
20260209095610OE4DNS-2>APLRG1,WIDE1-1,qAO,HA1KHJ-10:!L6:HMRg(^a GLoRa_APRS_iGate
20260209102621OE4DNS-2>APLRG1,WIDE1-1,qAO,HA1KHJ-10:!L6:HMRg(^a GLoRa_APRS_iGate
20260209105632OE4DNS-2>APLRG1,WIDE1-1,qAR,OE4ENU-LG:!L6:HMRg(^a GLoRa_APRS_iGate
20260209112653OE4DNS-2>APLRG1,WIDE1-1,qAO,HA1KHJ-10:!L6:HMRg(^a GLoRa_APRS_iGate
20260209115656OE4DNS-2>APLRG1,WIDE1-1,qAO,HA1KHJ-10:!L6:HMRg(^a GLoRa_APRS_iGate
20260209122706OE4DNS-2>APLRG1,WIDE1-1,qAO,HA1KHJ-10:!L6:HMRg(^a GLoRa_APRS_iGate
20260209125704OE4DNS-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6:HMRg(^a GLoRa_APRS_iGate
20260209132705OE4DNS-2>APLRG1,TCPIP*,qAC,T2FINLAND:!L6:HMRg(^a GLoRa_APRS_iGate
20260209135706OE4DNS-2>APLRG1,TCPIP*,qAC,T2TAS:!L6:HMRg(^a GLoRa_APRS_iGate
20260209142707OE4DNS-2>APLRG1,TCPIP*,qAC,T2TAS:!L6:HMRg(^a GLoRa_APRS_iGate
20260209145707OE4DNS-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6:HMRg(^a GLoRa_APRS_iGate