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
20170428235000VE7KWK-1>APU25N,qAR,VE7PKE:@282350z/5[K2/JHW_c2bg010t058r000p000P000h54b10271
20170429001000VE7KWK-1>APU25N,qAR,VE7PKE:@290010z/5[K2/JHW_X4bg010t058r000p000P000h54b10271
20170429003001VE7KWK-1>APU25N,qAR,VE7PKE:@290030z/5[K2/JHW_S2bg010t058r000p000P000h54b10270
20170429005002VE7KWK-1>APU25N,qAR,VE7PKE:@290050z/5[K2/JHW_W2bg010t057r000p000P000h54b10271
20170429011002VE7KWK-1>APU25N,qAR,VE7PKE:@290110z/5[K2/JHW_W.bg007t057r000p000P000h54b10271
20170429013001VE7KWK-1>APU25N,qAR,VE7PKE:@290130z/5[K2/JHW_Q.bg008t057r000p000P000h53b10271
20170429021004VE7KWK-1>APU25N,qAR,VE7PKE:@290210z/5[K2/JHW_U.bg008t056r000p000P000h55b10270