APRS Packet Errors for K0UND-1 (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
20260209150008K0UND-1>APRS,WIDE1-1,qAR,W1CDN-1:!4755.30N/09705.21W_250/008t034r000p000P000h86b10095 Bar=29.81in
20260209160011K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_270/009t036r000p000P000h81b10095 Bar=29.81in
20260209170005K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_280/011t037r000p000P000h75b10098 Bar=29.82in
20260209180007K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_290/010t037r000p000P000h75b10095 Bar=29.81in
20260209190008K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_280/009t037r000p000P000h75b10098 Bar=29.82in
20260209200007K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_270/010t037r000p000P000h75b10091 Bar=29.80in