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
20190618112727WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,W0ARP-3:=0000.00N/00000.00W_241/001g t045r000p019P h89b10110KDvs
20190618115727WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_223/004g t044r000p019P h89b10112KDvs
20190618125728WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_237/006g t046r000p019P h89b10115KDvs
20190618132729WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,W0ARP:=0000.00N/00000.00W_244/003g t049r000p019P h84b10116KDvs
20190618142730WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_251/001g t051r000p019P h76b10115KDvs