APRS Packet Errors for VE7KWK-1 (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
20170324002102VE7KWK-1>APU25N,qAo,VE7MKF-1:@240021z/5[K2/JHW_*4bg010t051r000p011P003h68b10138
20170324004103VE7KWK-1>APU25N,qAo,VE7MKF-1:@240041z/5[K2/JHW_+4bg009t051r000p004P003h68b10136
20170324010103VE7KWK-1>APU25N,qAR,VE7PKE:@240101z/5[K2/JHW_)2bg008t050r000p003P003h69b10133
20170324012104VE7KWK-1>APU25N,qAo,VE7MKF-1:@240121z/5[K2/JHW_*2bg011t050r000p003P003h70b10132
20170324014104VE7KWK-1>APU25N,qAo,VE7MKF-1:@240141z/5[K2/JHW_+2bg009t049r000p003P003h71b10133
20170324020108VE7KWK-1>APU25N,qAo,VE7MKF-1:@240201z/5[K2/JHW_)4bg009t049r000p003P003h72b10132