APRS Packet Errors for EA1FHY-9 (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
20260208172333EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1HTF-10:!/8uELI@q>!!Q
20260208172347EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8u_cLI>p>J@Q
20260208172427EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8ue:LI:(>J:Q
20260208172442EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8ug0LI62>J;Q
20260208172457EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8um0LI55>JKQ
20260208172512EA1FHY-9>APLRT1,WIDE1-1,qAR,ED1ZAT-10:!/8uo]LI2?>JHQ
20260208172527EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8unvLI/K>JAQ
20260208172542EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8ulBLI-2>J;Q
20260208174254EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8ul8LI,f>!!Q
20260208174344EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8un^LI.d>JHQ
20260208174400EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8uo+LI1;>JEQ
20260208174420EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8up"LI3l>JCQ
20260208174435EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8uk*LI5N>JCQ
20260208182903EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8uT&LIJf>!!Q
20260208182944EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8uRELIN2>JEQ
20260208183007EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8uN1LINy>J=Q
20260208183025EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8uJ?LINW>J.Q
20260208183056EA1FHY-9>APLRT1,WIDE1-1,qAO,EA1FHY-10:!/8uHRLIL>>J/Q