APRS Packet Errors for EA4PS (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
20190222011224EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222012852EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222014522EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222020150EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222021821EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222023503EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222025133EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222030802EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222032439EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222034109EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222035742EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222041416EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222043050EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222044722EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222050352EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222052021EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222053658EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222055328EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222061000EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222062634EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz
20190222064308EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1250 MHz