APRS Packet Errors for OK0BR-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
20261101140702OK0BR-10>APZ023,qAR,OK4MD-13:!4939.50uw49.10E&P8100 DIGI?*TA by*K5TVR AP
20261101144704OK0BR-10>APZ023,qAR,OK4MD-13:!4939.50NL0134|~1 *300DŇAJdyF/
20261101154707OK0BR-10>APZ023,qAR,OK4MD-13:!4939.50NL013>9.10E&PHG01000
20261101160708OK0BR-10>APZ023,qAR,OK4MD-13:!493?``GN01910E&HǸ(8D@O +@Q@b@/Kgfb w6
20261101162709OK0BR-10>APZ023,qAR,OK4MD-13:!49:6MO33Gg ~1`&A81000pA
20261101174713OK0BR-10>APZ023,qAR,OK4MD-13:!4939.50.*01769.10E&PHG002`A  o^A,by OK5R AP
20261101180715OK0BR-10>APZ023,qAR,OK4MD-13:!4939.50NL81;QTBjwLe/8d.يG5TVR AP