APRS Packet Errors for KB8PXM (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
20171022150325KB8PXM>BEACON,qAR,K8GPS-10:;146.67-R T719 Net Tue 9PM
20171022152327KB8PXM>BEACON,qAR,K8GPS-10:;146.67-R T719 Net Tue 9PM
20171022153326KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022154325KB8PXM>BEACON,qAR,K8GPS-10:;146.67-R T719 Net Tue 9PM
20171022155325KB8PXM>BEACON,qAR,K8GPS-10:;146.67-R T719 Net Tue 9PM
20171022160325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022161325KB8PXM>BEACON,qAR,K8GPS-10:;146.67-R T719 Net Tue 9PM
20171022162325KB8PXM>BEACON,qAR,K8GPS-10:;146.67-R T719 Net Tue 9PM
20171022171325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022173325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022183325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022184326KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022190325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022192325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022195325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022200325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022201325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM
20171022203325KB8PXM>BEACON,qAR,K8HSQ:;146.67-R T719 Net Tue 9PM