APRS Packet Errors for 1BATES-5 (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
202602081453241BATES-5>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081523241BATES-5>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081553251BATES-5>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081623251BATES-5>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081653251BATES-5>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081714591BATES-5>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081744581BATES-5>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081815001BATES-5>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081844591BATES-5>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081914581BATES-5>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602081945001BATES-5>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602082014591BATES-5>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.86SA05824.05W#PHG7550TEST en VHF
202602082044591BATES-5>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.86SA05824.05W#PHG7550TEST en VHF