APRS Packet Errors for YM2KDU (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
20171017072148YM2KDU>BEACON,LOCAL,qAR,TA1AST:;KARDUZ-R2*240057z4040.07N/03058.55r145.650MHz T088 -0600kHz
20171017074127YM2KDU>BEACON,LOCAL,qAR,TA1FL-12,TA1FL,T2CZECH:;KARDUZ-R2*240117z4040.07N/03058.55r145.650MHz T088 -0600kHz
20171017082053YM2KDU>BEACON,LOCAL,qAR,YM2KQ:;KARDUZ-R2*240157z4040.07N/03058.55r145.650MHz T088 -0600kHz
20171017085222YM2KDU>BEACON,LOCAL,qAR,YM2KQ:;KARDUZ-R2*240227z4040.07N/03058.55r145.650MHz T088 -0600kHz
20171017112100YM2KDU>BEACON,LOCAL,qAR,YM2KQ:;KARDUZ-R2*240457z4040.07N/03058.55r145.650MHz T088 -0600kHz
20171017113630YM2KDU>BEACON,LOCAL,qAR,YM2KQ:;KARDUZ-R2*240507z4040.07N/03058.55r145.650MHz T088 -0600kHz
20171017121609YM2KDU>BEACON,LOCAL,qAR,YM2KQ:;KARDUZ-R2*240547z4040.07N/03058.55r145.650MHz T088 -0600kHz
20171017130716YM2KDU>BEACON,LOCAL,qAR,YM2KQ:;KARDUZ-R2*240638z4040.07N/03058.55r145.650MHz T088 -0600kHz