APRS Packet Errors for AB4CZ-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
20260422181018AB4CZ-1>BEACON,WIDE2-2,qAR,W4BOC-1:!3359.98/8414.23W_
20260422184006AB4CZ-1>BEACON,WIDE2-2,qAR,W4BOC-1:!3359.98/8414.23W_
20260422191007AB4CZ-1>BEACON,WIDE2-2,qAR,W4BOC-1:!3359.98/8414.23W_
20260422194006AB4CZ-1>BEACON,WIDE2-2,qAR,W4BOC-1:!3359.98/8414.23W_
20260422194049AB4CZ-1>BEACON,KN6RO-13,KD4YDD-1*,qAR,AK4ZX-15:!3359.98/8414.23W_
20260422211006AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260422214021AB4CZ-1>BEACON,WIDE2-2,qAR,W4BOC-1:!3359.98/8414.23W_
20260422224006AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260422231006AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_