APRS Packet Errors for OK2JIB-10 (last 24 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
20251215012240OK2JIB-10>APLRw1,OK0BR-12*,qAR,OK4MD-13:!L4vL0RfBc`$MLÅRk ÁÐÒ !(Gaqe
20251215014240OK2JIB-10>APLRG1,OK0BR-12*,qAR,OK4MD-13:!LE,0b$Ffa GLoRa APRS iGate
20251215180238OK2JIB-10>APLRG1,OK0BR-12*,qAR,OK4MD-13:!L¤/`W"ƒ¦då GLoRá ÁPZ[ iGate
20251215202238OK2JIB-10>APLRG1,OK0BR-12*,qAO,OM7AMA-14:!L4vL0R‚ŠÊ=ÂçÄåha APRS iGate