APRS Packet Errors for OK0BR-12 (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
20260306092013OK0BR-12>APZ023,qAR,OK4MD-13:!493?î49NL 1349.09E&PHG01000 RX_Igate_LoRA by OK5TVR !P
20260306100015OK0BR-12>APZ023,qAR,OK4MD-13:!49£0·40GL01349.09E&PHF01000 RX_Igate_LoRA by OK5TVR AP
20260306142030OK0BR-12>APZ023,qAR,OK4MD-13:!4939.49NLð1349.09E&PHG01000 RX_Igate_LoRA by OK5TVR AP
20260306150032OK0BR-12>APZ023,qAR,OK4MD-13:!4939.49NL01349(PYC&PHG01000 RX_Igate_LoRA byLxõTV^,AP
20260306162036OK0BR-12>APZ023,qAR,OK4MD-13:!4939.49NM%$&µ9¦°±ESHv01000 RX_Igate_LoRA by OK5VVR
20260306182044OK0BR-12>APZ023,qAR,OK4MD-13:!4939.49.L6Q349.09E&PHGPPt0$dhzgate_LoRA by OK5TVR AP
20260306190046OK0BR-12>APZ023,qAR,OK4MD-13:!4399.49NL013ô9.0õE&PHG01000 RX_Igate_LoRA by OK5TVR AP
20260306220055OK0BR-12>APZ023,qAR,OK4MD-13:!493y*09Np1s”9.0“…&PHG
20260306224057OK0BR-12>APZ023,qAR,OK4MD-13:!4939.4901S49.09E&PHG01000 RX_Igate_LoRA by OK5TVR AP
20260306230058OK0BR-12>APZ023,qAR,OK4MD-13:!4939.49~|0249.09E&PHG01000`‚ÈØ:ate_LoRA by OK5TVR !V
20260307030111OK0BR-12>APZ023,qAR,OK4MD-13:!4939.49NL0734<+`iE&PHG01000 RX_Igate_LoRA by OK5TVR AP
20260307040114OK0BR-12>APZ021,qAR,OK4MD-13:!4939.49NL013=9.09E&ÉHG¹90°0 RX_Igate_LoRA by OK5TVR AP