APRS Packet Errors for DL2GCR-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
20260208133128DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208134628DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208140128DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208141628DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208143129DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208144629DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208150129DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208151629DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208153129DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208154629DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208160129DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208161629DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208163129DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208164629DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208170129DL2GCR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208171629DL2GCR-10>APLRG1,TCPIP*,qAC,T2PERTH:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208173130DL2GCR-10>APLRG1,TCPIP*,qAC,T2PERTH:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208174630DL2GCR-10>APLRG1,TCPIP*,qAC,T2PERTH:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208180130DL2GCR-10>APLRG1,TCPIP*,qAC,T2PERTH:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208181631DL2GCR-10>APLRG1,TCPIP*,qAC,T2PERTH:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208183130DL2GCR-10>APLRG1,TCPIP*,qAC,T2PERTH:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208184631DL2GCR-10>APLRG1,TCPIP*,qAC,T2PERTH:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208190131DL2GCR-10>APLRG1,TCPIP*,qAC,T2PERTH:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland
20260208191631DL2GCR-10>APLRG1,TCPIP*,qAC,T2PERTH:!L5otOPT-9a xGLora iGate in JN48CR im Badnerland