APRS Packet Errors for EA1HNC (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
20190121212637EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190121214243EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190121215852EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190121221514EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190121223116EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190121224730EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190121230341EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190121231944EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190121233551EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190121235157EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122000807EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122002406EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122004011EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122005613EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122011216EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122012819EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122014424EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122020030EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122021629EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122023238EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122024844EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190122030504EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz