APRS Packet Errors for EA1FAS (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
20261101144814EA1FAS>APDPRS,C4FM*,qAR,EA1URO-N:!0000.00N/00000.00E> FTM-400D via MMDVM
20261101144904EA1FAS>APDPRS,C4FM*,qAR,EA1URO-N:!0000.00N/00000.00E> FTM-400D via MMDVM
20261101144954EA1FAS>APDPRS,C4FM*,qAR,EA1URO-N:!0000.00N/00000.00E> FTM-400D via MMDVM
20261101145144EA1FAS>APDPRS,C4FM*,qAR,EA1URO-N:!0000.00N/00000.00E> FTM-400D via MMDVM
20261101145554EA1FAS>APDPRS,C4FM*,qAR,EA1URO-N:!0000.00N/00000.00E> FTM-400D via MMDVM
20261101145934EA1FAS>APDPRS,C4FM*,qAR,EA1URO-N:!0000.00N/00000.00E> FTM-400D via MMDVM
20261101154344EA1FAS>APDPRS,C4FM*,qAR,EA1URO-N:!0000.00N/00000.00E> FTM-400D via MMDVM
20261101172504EA1FAS>APDPRS,C4FM*,qAR,EA1URO-N:!0000.00N/00000.00E> FTM-400D via MMDVM