APRS Packet Errors for PegelUW (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
20251204085414DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_474
20251204100414DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_592
20251204110414DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_669
20251204111414DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_684
20251204130414DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_766
20251204140414DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_708
20251204141414DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_690
20251204142414DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_668
20251204143415DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_655
20251204144414DO5BX-1>APDW16,qAO,DO5BX-1:;PegelUW *111111z5303.61NP00851.24E_641