APRS Packet Errors for DJ0GX-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
20260209104321DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209105821DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209111321DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209112821DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209114321DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209115821DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209121322DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209122822DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209124322DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209125822DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209131322DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209132822DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209134322DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209135822DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209141322DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209142822DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209144322DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209145822DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209151322DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209152822DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209154322DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209155822DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209161322DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim
20260209162822DJ0GX-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L6$nOPMI(& xGLoRa APRS iGate RX Friesenheim