APRS Packet Errors for F6ZDV-3 (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
20260208144712F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208151722F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208154733F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208161743F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208164753F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208174814F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208181824F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208184834F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208191845F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208194855F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready
20260208201906F6ZDV-3>APRS,WIDE1-1,WIDE2-1,qAS,F1ZRP-13:=4921.36NL00602.77E&Solar 433.775 MHz Ready