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
20260208190010K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_170/015g021t028r000p000P000h74b10163 Bar=30.01in
20260208200004K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_170/016t030r000p000P000h69b10152 Bar=29.98in
20260208210006K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_180/017t030r000p000P000h74b10149 Bar=29.97in
20260208220005K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_180/018t030r000p000P000h80b10142 Bar=29.95in
20260208230007K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_170/016t030r000p000P000h80b10132 Bar=29.92in
20260209000006K0UND-1>APRS,WIDE1-1,qAO,N0RNB-5:!4755.30N/09705.21W_170/015t030r000p000P000h80b10129 Bar=29.91in