APRS Packet Errors for LU8ANB (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
20191016020203LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160402z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016023203LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160432z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016030203LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160502z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016033205LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160532z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016040148LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160601z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016043148LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160631z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016050215LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160702z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016053229LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160732z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016060253LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160802z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016063221LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160832z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016070257LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160902z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191016073254LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@160932z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1