APRS Packet Errors for IW3BVH-6 (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
20260420024056IW3BVH-6>APLRT1,WIDE1-1,qAR,IW3BVH-10:!/6yEdQ?Ss_ RQ.../...g...t075h31b10201
20260420025254IW3BVH-6>APLRT1,WIDE1-1,qAR,IW3BVH-10:!/6yF3Q?T;_ 9Q.../...g...t075h30b10130
20260420030806IW3BVH-6>APLRT1,WIDE1-1,qAR,IW3BVH-10:!/6yGCQ?T@_
20260420031809IW3BVH-6>APLRT1,WIDE1-1,qAR,IW3BVH-10:!/6yH@Q?T__ jQ.../...g...t075h30b10107
20260420035120IW3BVH-6>APLRT1,WIDE1-1,qAR,IW3BVH-10:!/6yG8Q?TZ_ "Q.../...g...t075h30b10115op.Davide 333 3535173|(e%V|
20260420041008IW3BVH-6>APLRT1,WIDE1-1,qAR,IW3BVH-10:!/6yHRQ?TL_ !Q.../...g...t075h30b10165
20260420042011IW3BVH-6>APLRT1,WIDE1-1,qAR,IW3BVH-10:!/6yE?Q?Tp_ JQ.../...g...t075h30b10136
20260420043056IW3BVH-6>APLRT1,WIDE1-1,qAR,IW3BVH-10:!/6yHKQ?Rc_ IQ.../...g...t075h30b10135
20260420063610IW3BVH-6>APLRT1,WIDE1-1,qAR,IW3BVH-10:!/6yH