APRS Packet Errors for EA3GKP (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
20190420123315EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201433z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420130319EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201503z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420133350EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201533z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420140337EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201603z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420143324EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201633z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420150340EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201703z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420153319EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201733z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420160336EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201803z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420163333EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201833z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420170332EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201903z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420173358EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@201933z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1
20190420180349EA3GKP>APRS,TCPIP*,qAS,BM2142POS:@202003z4122.100N/00206.85EQPi Star 433.4500/433.4500 CC1