APRS Packet Errors for IU3CLX-14 (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
20251009150607IU3CLX-14>APLRT1,WIDE1-1,qAO,S53SA-11:!/7HJ)QzO?_ LQ.../...g...t067h68b10219
20251009152615IU3CLX-14>APLRT1,WIDE1-1,qAO,S53SA-11:!/7HL.QzP4_ $Q.../...g...t065h76b10231
20251009171625IU3CLX-14>APLRT1,IR3H*,qAR,IU3BRB-10:!/7@+[QdwZu4DÑ
20251009181300IU3CLX-14>APLRT1,WIDE1-1,qAO,IR3UAC-10:!/7LeUQW#/_ oQ.../...g...t059h00b10239
20251009190320IU3CLX-14>APLRT1,WIDE1-1,qAO,IR3UAC-10:!/7LeSQW#-_ 7Q.../...g...t057h00b10239
20251009193332IU3CLX-14>APLRT1,WIDE1-1,qAO,IR3UAC-10:!/7Le_QW#*_ 6Q.../...g...t058h00b10245
20251009200344IU3CLX-14>APLRT1,WIDE1-1,qAO,IR3UAC-10:!/7LeJQW#-_ 7Q.../...g...t061h00b10245
20251009201348IU3CLX-14>APLRT1,WIDE1-1,qAO,IR3UAC-10:!/7LeSQW#(_ tQ.../...g...t061h00b10246
20251009202352IU3CLX-14>APLRT1,WIDE1-1,qAO,IR3UAC-10:!/7LeKQW#%_ !Q.../...g...t062h00b10246