APRS Packet Errors for EA5SW (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
20190222050730EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222052349EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222054010EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222055629EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222061249EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222062909EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222064531EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222070151EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222071812EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222073432EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222075055EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222080715EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222082335EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222083956EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222085618EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222091238EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222092858EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222094518EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222100141EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222101801EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222103421EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190222105041EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz