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
20190418091408EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418093046EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418094731EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418100413EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418102050EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418103724EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418105405EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418111042EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418112716EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418114354EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418120030EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418121703EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418123341EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418125017EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418130654EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418132330EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418134004EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418135647EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418141328EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418143009EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418144647EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz
20190418150328EA4PS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4PS-DP!4025.90N/-03-49.31rRNG0034 IPSC2-EA1Master MMDVM 435.1250 MHz