APRS Packet Errors for EA4GRR (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
20190219083107EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219084739EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219090420EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219092059EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219093739EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219095409EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219101054EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219102752EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219104429EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219110116EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219111812EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219113502EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219115153EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219120834EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219122519EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219124206EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219125855EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219131541EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219134920EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219140557EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190219142238EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz