APRS Packet Errors for EA4EWX (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
20190616090700EA4EWX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4EWX-DP!387600.00N/-05-43.rRNG0034 IPSC2-EA4Master MMDVM 438.9125 MHz
20190616092414EA4EWX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4EWX-DP!387600.00N/-05-43.rRNG0034 IPSC2-EA4Master MMDVM 438.9125 MHz
20190616094115EA4EWX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4EWX-DP!387600.00N/-05-43.rRNG0034 IPSC2-EA4Master MMDVM 438.9125 MHz
20190616095812EA4EWX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4EWX-DP!387600.00N/-05-43.rRNG0034 IPSC2-EA4Master MMDVM 438.9125 MHz
20190616101515EA4EWX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4EWX-DP!387600.00N/-05-43.rRNG0034 IPSC2-EA4Master MMDVM 438.9125 MHz
20190616103212EA4EWX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4EWX-DP!387600.00N/-05-43.rRNG0034 IPSC2-EA4Master MMDVM 438.9125 MHz
20190616104936EA4EWX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4EWX-DP!387600.00N/-05-43.rRNG0034 IPSC2-EA4Master MMDVM 438.9125 MHz
20190616110659EA4EWX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4EWX-DP!387600.00N/-05-43.rRNG0034 IPSC2-EA4Master MMDVM 438.9125 MHz