APRS Packet Errors for UB6YDG-Y (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
20260819080956UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819081559UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819081839UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819084320UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819084530UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819085822UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819094312UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819094402UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819100114UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819100214UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM
20260819100544UB6YDG-Y>APDPRS,C4FM*,qAR,UB6YDG-R:!0000.00N/00000.00E[ FT-5D via MMDVM