APRS Packet Errors for OK0BBK-2 (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
20260731100035OK0BBK-2>APOT21,OK0BR-1*,WIDE2-1,qAR,OE3VPA-10:!5035.61NS015
20260731104402OK0BBK-2>APOT21,OK0BR-1*,WIDE2-1,qAR,DB0FBG:!5035.61ŽS01515.80E# 12.4V 29C PHG34606/Test Kozakov
20260731130308OK0BBK-2>APOT21,OK0BR-1*,WIDE2-1,qAR,OE3VPA-10:!5035.61NS01515.80…# 12.4V 29C PHG34606/Tept Kozakov
20260731195928OK0BBK-2>APOT21,OK0ZRJ-2,OK0BR-1*,qAR,OE3EMC-10:!5°25.61NS01515.80E# 12.4V 31C PHG34606/Test Kozakov
20260801064109OK0BBK-2>APOT21,OK0BAD-2,OK0BR-1*,qAR,OK2JIB-1:!5035.61NS01515.¸1E# 12.4V@ 29ƒ PHG34606/Test Kozakov