APRS Packet Errors for OK4MD-15 (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
20260208163950OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208170850OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208173750OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208180650OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208183550OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208190450OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208193350OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208200250OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208203150OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208204351OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208211251OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208214151OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate
20260208221051OK4MD-15>APLRG1,TCPIP*,qAC,T2CZECH:!L4nO]R:m4& GLoRa APRS iGate