APRS Packet Errors for EA5CH (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
20190819164845EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819170554EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819172302EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819174012EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819175723EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819181436EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819183142EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819184851EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819190606EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819192316EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819194024EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819195721EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819201426EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819203118EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819204813EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819210511EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819212207EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819213908EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819215611EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819221305EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190819223011EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz