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
20250918143338IU3CLX-14>APLRT1,WIDE1-1,qAO,IZ3ZLB-10:!/7CYAQS;l_ !Q.../...g...t088h34b10266
20250918144342IU3CLX-14>APLRT1,WIDE1-1,qAO,IQ3VV-10:!/7CYUQS;b_ iQ.../...g...t088h34b10278
20250918145346IU3CLX-14>APLRT1,WIDE1-1,qAO,IQ3VV-10:!/7CY7QS;`_ @Q.../...g...t087h37b10270
20250918150350IU3CLX-14>APLRT1,WIDE1-1,qAR,IQ3QR-10:!/7CY7QS;X_ HQ.../...g...t085h36b10272LoRa Truck
20250918151354IU3CLX-14>APLRT1,WIDE1-1,qAR,IQ3QR-10:!/7CY@QS;]_ qQ.../...g...t084h37b10262
20250918151440IU3CLX-14>APLRT1,WIDE1-1,qAO,IQ3VV-10:!/7CY@QS;]_ qQ.../...g...t084h37b10262
20250918152358IU3CLX-14>APLRT1,WIDE1-1,qAO,IQ3VV-10:!/7CY2QS;T_ sQ.../...g...t082h40b10263
20250918153402IU3CLX-14>APLRT1,WIDE1-1,qAO,IQ3VV-10:!/7CYAQS;[_ NQ.../...g...t082h39b10273
20250918154406IU3CLX-14>APLRT1,WIDE1-1,qAO,IQ3VV-10:!/7CYLQS;X_ -Q.../...g...t081h44b10252
20250918174027IU3CLX-14>APLRT1,WIDE1-1,qAR,IQ3QR-10:!/7=n4QNP[_ /Q.../...g...t065h79b10268