APRS Packet Errors for EA1GLE (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
20200216143306EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@161533z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216150253EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@161602z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216153231EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@161632z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216160323EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@161703z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216163255EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@161732z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216170218EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@161802z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216173232EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@161832z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216180331EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@161903z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216183305EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@161933z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216190347EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@162003z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216193323EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@162033z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1
20200216200305EA1GLE>APRS,TCPIP*,qAS,BM2142POS:@162103z4143.100N/05023.99WrBurgos 224.9400/222.3400 CC1