APRS Packet Errors for KE5BRG (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
20260209123820KE5BRG>APBTUV,W5PFC-2,WIDE1*,WIDE2-1,qAO,K5LVL-2:=3225.10N/09001.13W>066/000/A=0003087.19V
20260209130820KE5BRG>APBTUV,W5PFC-2,WIDE1*,WIDE2-1,qAO,KI5HZZ-10:=3225.10N/09001.13W>066/000/A=0003057.14V
20260209131026KE5BRG>APBTUV,W5PFC-2,WIDE1,AI5BL-1,WIDE2*,qAO,KJ5HTB-2:=3225.10N/09001.13W>066/000/A=0003057.14V
20260209134806KE5BRG>APBTUV,W5PFC-2,WIDE1*,WIDE2-1,qAO,KI5HZZ-10:=3223.97N/09001.31W>225/048/A=0003017.09V
20260209135100KE5BRG>APBTUV,W5PFC-2,WIDE1*,WIDE2-1,qAO,KI5HZZ-10:=3222.98N/09002.53W>278/012/A=0003217.10V
20260209135400KE5BRG>APBTUV,W5PFC-2,WIDE1*,WIDE2-1,qAR,KC5TGT-10:=3224.52N/09004.93W>307/049/A=0002917.12V
20260209151800KE5BRG>APBTUV,W5PFC-2*,WIDE1,WIDE2-1,qAR,W9NG-10:=3218.97N/09010.82W>146/000/A=0003416.99V