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
20171218174832VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@181748z/5[K2/JHW_2bg006t042r000p186P004h96b10188
20171218180831VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@181808z/5[K2/JHW_b)bg004t042r000p185P004h95b10190
20171218182836VE7KWK-1>WIDE1-1,WIDE2-1,qAR,KF7DRV-3:@181828z/5[K2/JHW_h.bg007t043r000p183P004h94b10191
20171218184837VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@181848z/5[K2/JHW__!bg003t043r000p179P004h95b10196
20171218190837VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@181908z/5[K2/JHW_a!bg002t043r000p178P004h92b10195
20171218192836VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@181928z/5[K2/JHW_a)bg004t044r000p176P004h92b10198
20171218194836VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@181948z/5[K2/JHW_a)bg006t044r000p171P004h90b10198
20171218200836VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@182008z/5[K2/JHW_c.bg008t044r000p170P004h90b10198
20171218202839VE7KWK-1>WIDE1-1,WIDE2-1,qAR,VE7PKE:@182028z/5[K2/JHW_c)bg006t044r000p168P004h89b10201