APRS Packet Errors for EA5RCE (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
20190320174155EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320175848EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320181535EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320183226EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320184919EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320190612EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320192318EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320194014EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320195710EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320201415EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320203111EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320204750EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320210440EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320212118EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320213811EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320215453EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320221136EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320222815EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320224454EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320230136EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190320231818EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz