APRS Packet Errors for EA7HGI (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
20190326190311EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190326190323EA7HGI>APRS,TCPIP*,qAS,BM2142POS:@262003z3645.33N/00254.93WQPHG1050MMDVM DMO 430.4000/430.4000 CC1
20190326192033EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326193320EA7HGI>APRS,TCPIP*,qAS,BM2142POS:@262033z3645.33N/00254.93WQPHG1050MMDVM DMO 430.4000/430.4000 CC1
20190326193734EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326195447EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326200322EA7HGI>APRS,TCPIP*,qAS,BM2142POS:@262103z3645.33N/00254.93WQPHG1050MMDVM DMO 430.4000/430.4000 CC1
20190326201140EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326202837EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326203318EA7HGI>APRS,TCPIP*,qAS,BM2142POS:@262133z3645.33N/00254.93WQPHG1050MMDVM DMO 430.4000/430.4000 CC1
20190326204537EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326210237EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326211943EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326213643EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326215341EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326221041EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326222739EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326224438EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326230129EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326231817EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326233513EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190326235157EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190327000838EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190327002524EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz
20190327004211EA7HGI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HGI-DP!3645.33N/-02-54.93rRNG0034 IPSC2-EA4Master MMDVM 144.8125 MHz