APRS Packet Errors for EA1IGN (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
20181019191224EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019192754EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019194345EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019195915EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019201436EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019202958EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019204523EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019210045EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019211604EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019213125EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019214648EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019220208EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019221726EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019223245EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019224806EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019230325EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019231844EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019233403EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181019234926EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181020000445EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181020002004EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181020003523EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz
20181020005044EA1IGN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IGN-DP!4058.72N/-05-40.59rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4000 MHz