APRS Packet Errors for AB4CZ-1 (last 24 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
20260315114015AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260315141015AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260315144014AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260315154029AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260315164015AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260315181014AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260315184012AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260315194015AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260315194219AB4CZ-1>BEACON,AJ4FJ-5,KD4YDD-1*,qAR,KC4SAR-5:!3359.98/8414.23W_
20260315204015AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260315211012AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260316034012AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260316044014AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260316091018AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260316104011AB4CZ-1>BEACON,WIDE2-2,qAR,N4NE-2:!3359.98/8414.23W_
20260316104044AB4CZ-1>BEACON,KN6RO-13*,WIDE2-1,qAO,N4DKN-10:!3359.98/8414.23W_