APRS Packet Errors for N4HYK (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
20190122161453N4HYK>APDPRS,C4FM*,qAR,N4HYK-N:!0000.00N/00000.00E[ FT-2D via MMDVM
20190122230713N4HYK>APDPRS,C4FM*,qAR,N4HYK-N:!0000.00N/00000.00E[ FT-2D via MMDVM
20190123022512N4HYK>APDPRS,C4FM*,qAR,N4HYK-N:!0000.00N/00000.00E[ FT-2D via MMDVM
20190123022602N4HYK>APDPRS,C4FM*,qAR,N4HYK-N:!0000.00N/00000.00E[ FT-2D via MMDVM
20190123022712N4HYK>APDPRS,C4FM*,qAR,N4HYK-N:!0000.00N/00000.00E[ FT-2D via MMDVM
20190123023842N4HYK>APDPRS,C4FM*,qAR,N4HYK-N:!0000.00N/00000.00E[ FT-2D via MMDVM
20190123023922N4HYK>APDPRS,C4FM*,qAR,N4HYK-N:!0000.00N/00000.00E[ FT-2D via MMDVM
20190123024022N4HYK>APDPRS,C4FM*,qAR,N4HYK-N:!0000.00N/00000.00E[ FT-2D via MMDVM
20190123024102N4HYK>APDPRS,C4FM*,qAR,N4HYK-N:!0000.00N/00000.00E[ FT-2D via MMDVM