APRS Packet Errors for W4CVY/1 (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
20260208152121W4CVY>APN382,qAR,N4MAR:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208154121W4CVY>APN382,qAR,N4MAR:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208160121W4CVY>APN382,qAR,N4MAR:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208162121W4CVY>APN382,qAR,N4MAR:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208164121W4CVY>APN382,qAR,N4MAR:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208170122W4CVY>APN382,qAO,W4RDZ-2:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208172121W4CVY>APN382,qAO,W4RDZ-2:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208174121W4CVY>APN382,qAO,W4RDZ-2:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208180121W4CVY>APN382,qAR,N4MAR:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208182121W4CVY>APN382,qAR,N4MAR:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208194121W4CVY>APN382,qAR,N4MAR:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m
20260208202121W4CVY>APN382,qAR,N4MAR:;W4CVY/1 *111111z3227.99N/08503.36Wr146.880MHz T123 -060 R25m