APRS Packet Errors for KO6BPG-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
20250823041541KO6BPG-10>APDW17,KF6ILA-10*,qAO,KD6LPA:!3249.84NS11712.W4W#PHG2020APRS IGATE DIGI
20250823044253KO6BPG-10>APIN21,KM6KID-9,KF6ILA-10,WIDE2*,qAO,KD6LPA:!3249.8 N11712.77W#any lone at 778uv
20250823063540KO6BPG-10>APDW17,KF6ILA-10*,qAR,KF6NXQ-15:!329.84NS11712.74W#PHG2020APRS IGATE DIGI
20250823073055KO6BPG-10>AVIN21,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:!3249.89N1171*.77W#any tome at 778uv
20250823075859KO6BPG-10>APIN21,KM6KID-9,KF6ILA-10,WIDE2*,qAR,KF6NXQ-15:!3249.89N11712.77×"any tone at 778sv
20250823081041KO6BPG-10>APDW17,KF6ILA-10*,qAR,KF6NXQ-15:!3249.84NSą0712.74W#PHG2020APRS IGATE DIGI
20250823081457KO6BPG-10>APIN21,KF6ILA-10*,WIDE2-1,qAO,KD6LPA:!3249.8YN11712.77W#any tone at 778uv
20250823085858KO6BPG-10>APIN21,KF6ILA-10*,WIDE2-1,qAR,KF6NXQ-15:!32t8.89N11712.77W#any tove at877 uv
20250823090458KO6BPG-10>APIN21,KF6ILA-10*,WIDE2-1,qAO,KD6LPA:!32*9.89N11712.77W#any tone at 778uv
20250823093059KO6BPG-10>APIN21,KF6ILA-10*,WIDE2-1,qAO,KD6LPA:!3249.89N1171277W#any ton at 778uvi
20250823095040KO6BPG-10>APDW17,KF6ILA-10*,qAR,KN6RBP-10:!3249.84NS11712.ˇ5W#PHG2020APRS IGATE DIGI