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
20181209155139EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209160712EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209162237EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209163808EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209165344EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209170907EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209172433EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209174007EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209175544EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209181111EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209182646EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209184227EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209185753EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209191317EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209192841EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209194408EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209195931EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209201457EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209203020EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209204548EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209210116EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209211641EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz
20181209213203EA7JV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JV-DP!3727.77N/-03-28.36rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9125 MHz