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
20190823142803EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823144515EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823150218EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823151927EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823153632EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823155342EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823161051EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823162802EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823164512EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823170227EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823171937EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823173646EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823175355EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823181102EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823182808EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823184514EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823190214EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823191921EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823193618EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823195332EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20190823201044EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz