APRS Packet Errors for 431.90-16 (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
20260208134547F5ZZJ-4>APNU3B,F5ZDQ*,WIDE2-1,qAR,F1ZNT-3:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625
20260208141607F5ZZJ-4>APNU3B,WIDE2-1,qAO,F1ZNO:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625
20260208144629F5ZZJ-4>APNU3B,F5ZDQ*,WIDE2-1,qAR,F1ZNT-3:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625
20260208151652F5ZZJ-4>APNU3B,F5ZDQ*,WIDE2-1,qAR,F1ZNT-3:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625
20260208161736F5ZZJ-4>APNU3B,WIDE2-1,qAO,F1ZNO:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625
20260208164759F5ZZJ-4>APNU3B,F5ZDQ*,WIDE2-1,qAR,F1ZNT-3:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625
20260208171822F5ZZJ-4>APNU3B,F5ZDQ*,WIDE2-1,qAR,F1ZNT-3:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625
20260208174844F5ZZJ-4>APNU3B,F5ZWW-3*,WIDE2-1,qAR,F5LHI-11:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625
20260208181907F5ZZJ-4>APNU3B,F5ZDQ*,WIDE2-1,qAR,F1ZNT-3:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625
20260208184929F5ZZJ-4>APNU3B,F5ZDQ*,WIDE2-1,qAR,F1ZNT-3:;431.90-16*111111z4407.40N/00547.88Er 1750 200K QRG LOC 145.2625