APRS Packet Errors for KC3BHK-2 (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
20260209151114	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_
20260209154149	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_
20260209161226	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_
20260209164301	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_
20260209171334	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_
20260209174407	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_
20260209181439	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_
20260209184512	KC3BHK-2>APTW01,N3KTX-2*,WIDE1,qAR,W3AD-1:!3922.63N/07727.86W_
20260209191543	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_
20260209194616	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_
20260209201649	KC3BHK-2>APTW01,WIDE1-1,qAR,KC3BHK-1:!3922.63N/07727.86W_