APRS Packet Errors for 1BATES-3 (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
202602091033521BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091103511BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091133511BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091203521BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091233531BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091303521BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091333521BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091403521BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091433531BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091503531BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091533531BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF
202602091603521BATES-3>APE32A,WIDE2-2,qAO,LW5DB-1:!3435.86SA05824.05W#PHG7550TEST en UHF