APRS Packet Errors for WA4WLF (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
20260208143127WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#217/000/A=00088913.88V
20260208150128WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#217/000/A=00089513.86V
20260208153127WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.97W#217/000/A=00083013.88V
20260208160127WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#217/000/A=00085313.86V
20260208163129WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#020/000/A=00086613.86V
20260208170129WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#188/000/A=00083613.90V
20260208173131WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#148/000/A=00084613.88V
20260208180305WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#230/000/A=00088913.84V
20260208183805WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#222/000/A=00087213.86V
20260208190943WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#150/000/A=00087213.85V
20260208193945WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.97W#331/000/A=00086613.88V
20260208201003WA4WLF>APN000,WIDE1-1,WIDE2-1,qAO,N5IRU:=3610.47N/09545.98W#348/000/A=00086613.87V