APRS Packet Errors for EA7JV (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
20190825033127EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825034817EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825040508EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825042204EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825043855EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825045546EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825051235EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825052928EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825054617EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825060309EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825061959EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825063652EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825065353EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825071052EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825072745EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825074440EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825080134EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825081828EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825083529EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825085226EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190825090923EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz