APRS Packet Errors for WB7BKM-13 (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
20181217061726WB7BKM-13>APK102,WALDEN,WIDE1,WERNER,WIDE2*,qAR,CEDAR:=09H6.00N/202E9.00p_273/011g t037r000p000P h34b10230KDvs
20181217061848WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_273/011g t037r000p000P h34b10230KDvs
20181217071904WB7BKM-13>APK102,WALDEN,WIDE1,ERIDGE,WIDE2*,qAR,SUNLGT:=09H6.00N/202E9.00p_255/012g t036r000p000P h36b10229KDvs
20181217081727WB7BKM-13>APK102,WALDEN,WIDE1,WERNER,WIDE2*,qAR,CEDAR:=09H6.00N/202E9.00p_248/016g t035r000p000P h37b10220KDvs
20181217081838WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_248/016g t035r000p000P h37b10220KDvs
20181217084729WB7BKM-13>APK102,WALDEN,WIDE1,WERNER,WIDE2*,qAR,CEDAR:=09H6.00N/202E9.00p_264/014g t034r000p000P h37b10219KDvs
20181217084812WB7BKM-13>APK102,WALDEN,WIDE1,DTSERO,WIDE2*,qAR,SUNLGT:=09H6.00N/202E9.00p_264/014g t034r000p000P h37b10219KDvs