APRS Packet Errors for SM7CKM-9 (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
20251205202055SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!Šd@eð`*0,l5>v/Ron on the road 13.95V"3t}
20251205214635SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.11N/01435.9059On The Road Again
20251205215514SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.11N/01435.9’ˆŠd@eð
20251205220544SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.12N/01435.9
20251205222041SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.13N/01436.0
20251205222736SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.10N8E>358/000/A=000118On The Road Again
20251205224455SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.13N/01436.0
20251205231804SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.09N360On The Road Again
20251206001417SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!8E>203/001/A=000278On The Road Again
20251206001511SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.10N/01436.0
20251206010912SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.14N/01436.0e Road Again
20251206020043SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!460/APRS DIGI UIDIGI 1.9b3 only WIDEn-n
20251206020903SM7CKM-9>APAT51,SK7HW-2*,WIDE2-1,qAR,SA7AHC-1:!5704.13N170On The Road Again