APRS Packet Errors for DL4MN-13 (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
20260208201218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260208204218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260208211218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260208214218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260208221218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260208224218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260208231218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260208234218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260209001218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260209004218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260209011218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU
20260209014218DL4MN-13>APLRG1,TCPIP*,qAC,T2CZECH:!L4:GAQ5U*& GLoRa iGate 433.750 MHz JO51JU