APRS Packet Errors for EA3HYZ (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
20190221160548EA3HYZ>APRS,TCPIP*,qAS,BM2142POS:@211705z4135.100N/00236.00EQPHG3090Frecuencia 1ª: DMO, 2ª MMVDM 0.0004/0.0004 CC1
20190221163624EA3HYZ>APRS,TCPIP*,qAS,BM2142POS:@211736z4135.100N/00236.00EQPHG3090Frecuencia 1ª: DMO, 2ª MMVDM 0.0004/0.0004 CC1
20190221170607EA3HYZ>APRS,TCPIP*,qAS,BM2142POS:@211806z4135.100N/00236.00EQPHG3090Frecuencia 1ª: DMO, 2ª MMVDM 0.0004/0.0004 CC1
20190221173552EA3HYZ>APRS,TCPIP*,qAS,BM2142POS:@211835z4135.100N/00236.00EQPHG3090Frecuencia 1ª: DMO, 2ª MMVDM 0.0004/0.0004 CC1
20190221180612EA3HYZ>APRS,TCPIP*,qAS,BM2142POS:@211906z4135.100N/00236.00EQPHG3090Frecuencia 1ª: DMO, 2ª MMVDM 0.0004/0.0004 CC1
20190221183605EA3HYZ>APRS,TCPIP*,qAS,BM2142POS:@211936z4135.100N/00236.00EQPHG3090Frecuencia 1ª: DMO, 2ª MMVDM 0.0004/0.0004 CC1
20190221190600EA3HYZ>APRS,TCPIP*,qAS,BM2142POS:@212005z4135.100N/00236.00EQPHG3090Frecuencia 1ª: DMO, 2ª MMVDM 0.0004/0.0004 CC1
20190221193640EA3HYZ>APRS,TCPIP*,qAS,BM2142POS:@212036z4135.100N/00236.00EQPHG3090Frecuencia 1ª: DMO, 2ª MMVDM 0.0004/0.0004 CC1
20190221200634EA3HYZ>APRS,TCPIP*,qAS,BM2142POS:@212106z4135.100N/00236.00EQPHG3090Frecuencia 1ª: DMO, 2ª MMVDM 0.0004/0.0004 CC1