APRS Packet Errors for BI4AII-4 (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
20260208133316BI4AII-4>DM9100,WIDE2-2,qAO,BG4FRZ-10:!3113.97N/12126.72Ey
20260208140400BI4AII-4>DM9100,WIDE2-2,qAO,BG4FRZ-10:!3113.97N/12126.72Ey
20260208143717BI4AII-4>DM9100,WIDE2-2,qAO,BG4FRZ-10:!3113.97N/12126.72Ey
20260208150804BI4AII-4>DM9100,WIDE2-2,qAO,BG4FRZ-10:!3113.97N/12126.72Ey
20260208154020BI4AII-4>DM9100,WIDE2-2,qAO,BG4FRZ-10:!3113.97N/12126.72Ey
20260208161052BI4AII-4>DM9100,WIDE2-2,qAS,BH4DBZ-10:!3113.97N/12126.72Ey
20260208164116BI4AII-4>DM9100,WIDE2-2,qAO,BG4FRZ-10:!3113.97N/12126.72Ey
20260208171147BI4AII-4>DM9100,WIDE2-2,qAO,BG4FRZ-10:!3113.96N/12126.72Ey
20260208174217BI4AII-4>DM9100,WIDE2-2,qAS,BH4DBZ-10:!3113.96N/12126.72Ey
20260208181241BI4AII-4>DM9100,WIDE2-2,qAO,BG4FRZ-10:!3113.96N/12126.72Ey
20260208184306BI4AII-4>DM9100,WIDE2-2,qAO,BG4FRZ-10:!3113.97N/12126.72Ey