APRS Packet Errors for EA1URE-10 (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
20260208145910EA1URE-10>APLRG1,WIDE1-1,qAO,EA1FHY-10:!L8xV
20260208153010EA1URE-10>APLRG1,WIDE1-1,qAO,EA1DLB-10:!L8xV
20260208160111EA1URE-10>APLRG1,WIDE1-1,qAR,ED1ZAT-10:!L8xV
20260208163211EA1URE-10>APLRG1,WIDE1-1,qAR,ED1ZAR-10:!L8xV
20260208170311EA1URE-10>APLRG1,WIDE1-1,qAR,ED1ZAR-10:!L8xV
20260208173414EA1URE-10>APLRG1,WIDE1-1,qAO,EA1FHY-10:!L8xV
20260208173538EA1URE-10>APLRG1,EA1BVF-10*,qAO,EB1GEM-10:!L8xV
20260208180512EA1URE-10>APLRG1,WIDE1-1,qAR,ED1ZAR-10:!L8xV
20260208183613EA1URE-10>APLRG1,WIDE1-1,qAO,EA1JAV-10:!L8xV
20260208190713EA1URE-10>APLRG1,WIDE1-1,qAR,ED1ZAX-10:!L8xV
20260208193813EA1URE-10>APLRG1,WIDE1-1,qAO,EA1FHY-10:!L8xV
20260208200914EA1URE-10>APLRG1,WIDE1-1,qAO,EA1FHY-10:!L8xV
20260208204014EA1URE-10>APLRG1,WIDE1-1,qAR,ED1ZAR-10:!L8xV