APRS Packet Errors for WA1VIN-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
20260208135525WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.03W[ FT-5D via MMDVM
20260208135640WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.03W[ FT-5D via MMDVM
20260208150100WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.02W[ FT-5D via MMDVM
20260208150150WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.02W[ FT-5D via MMDVM
20260208150310WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.02W[ FT-5D via MMDVM
20260208150400WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.02W[ FT-5D via MMDVM
20260208150450WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.02W[ FT-5D via MMDVM
20260208150550WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.03W[ FT-5D via MMDVM
20260208150720WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.02W[ FT-5D via MMDVM
20260208150920WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.03W[ FT-5D via MMDVM
20260208151040WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.03W[ FT-5D via MMDVM
20260208151240WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.06N/07149.03W[ FT-5D via MMDVM
20260208151440WA1VIN-Y>APDPRS,C4FM*,qAR,WA1VIN-N:!4122.07N/07149.03W[ FT-5D via MMDVM