APRS Packet Errors for YO5ZF-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
20261101074426	YO5ZF-1>APRS,ED1YAP-3,WIDE2*,qAR,ED1ZAR-3:!0000.00N/00000.00W>199 55 60 270 42 m320 M122 r168
20261101075619	YO5ZF-1>APRS,ED1YAP-3,WIDE2*,qAR,ED1ZAR-3:!0000.00N/00000.00W>221 65 60 287 42 a1 d0 h7
20261101080806	YO5ZF-1>APRS,ED1YAP-3,WIDE2*,qAR,ED1ZAR-3:!0000.00N/00000.00W>218 60 56 284 42 m320 M122 r168
20261101080924	YO5ZF-1>APRS,ED1YAP-3,WIDE2*,qAR,ED1ZAR-3:!0000.00N/00000.00W>217 64 51 294 42 m320 M122 r169
20261101085140	YO5ZF-1>APRS,ED1YAP-3,WIDE2*,qAR,ED1ZAR-3:!0000.00N/00000.00W>218 77 41 301 42 m320 M122 r170