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
20251008214712IU3CLX-14>APLRT1,IQ4FE-3*,qAR,I4VBO-20:!/7NY1Q*DM_ #Q.../...g...t053h00b10227
20251008224736IU3CLX-14>APLRT1,IQ4FE-3*,qAR,I4VBO-20:!/7NYJQ*DJ_ iQ.../...g...t051h00b10221LoRa Truck
20251008230744IU3CLX-14>APLRT1,IQ4FE-3*,qAR,I4VBO-20:!/7NYAQ*D>_ NQ.../...g...t051h00b10214
20251008232752IU3CLX-14>APLRT1,IQ4FE-3*,qAR,I4VBO-20:!/7NYUQ*DE_ BQ.../...g...t051h00b10210
20251008234800IU3CLX-14>APLRT1,IQ4FE-3*,qAR,I4VBO-20:!/7NYJQ*DJ_
20251009003821IU3CLX-14>APLRT1,IQ4FE-3*,qAR,I4VBO-20:!/7NYJQ*DV_ EQ.../...g...t054h00b10208
20251009023908IU3CLX-14>APLRT1,IQ4FE-3*,qAR,I4VBO-20:!/7NYFQ*DJ_ XQ.../...g...t053h00b10209