APRS Packet Errors for IR0ZZW (last 24 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
20251014035753IR0ZZW>APRS,TCPIP,IW0DFE-10*,qAR,IZ0FKE-6:;;EL-IR0ZZW*111111z4152.95NE01230.93E0145.312MHz T000 R05m SvxLink by SM0SVX (www.svxlink.org
20251014041753IR0ZZW>APRS,TCPIP,IW0DFE-10*,qAR,IZ0FKE-6:;;EL-IR0ZZW*111111z4152.95N101230.93E0145.312MHz T000 R05m SvxLink by SM0SVX (www.svxlink.org
20251014042753IR0ZZW>APRS,TCPIP,IW0DFE-10*,qAR,IZ0FKE-6:;;EL-IR0ZZW*111111z4152.95N201230.93E0145.312MHz T000 R05m SvxLink by SM0SVX (www.svxlink.org
20251014045753IR0ZZW>APRS,TCPIP,IW0DFE-10*,qAR,IZ0FKE-6:;;EL-IR0ZZW*111111z4152.95N301230.93E0145.312MHz T000 R05m SvxLink by SM0SVX (www.svxlink.org
20251014062753IR0ZZW>APRS,TCPIP,IW0DFE-10*,qAR,IZ0FKE-6:;;EL-IR0ZZW*111111z4152.95N201230.93E0145.312MHz T000 R05m SvxLink by SM0SVX (www.svxlink.org
20251014064753IR0ZZW>APRS,TCPIP,IW0DFE-10*,qAR,IZ0FKE-6:;;EL-IR0ZZW*111111z4152.95N101230.93E0145.312MHz T000 R05m SvxLink by SM0SVX (www.svxlink.org
20251014065753IR0ZZW>APRS,TCPIP,IW0DFE-10*,qAR,IZ0FKE-6:;;EL-IR0ZZW*111111z4152.95NE01230.93E0145.312MHz T000 R05m SvxLink by SM0SVX (www.svxlink.org
20251014075753IR0ZZW>APRS,TCPIP,IW0DFE-10*,qAR,IZ0FKE-6:;;EL-IR0ZZW*111111z4152.95NE01230.93E0145.312MHz T000 R05m SvxLink by SM0SVX (www.svxlink.org