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
20191121053032LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@210630z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121060032LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@210700z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121063051LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@210730z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121070053LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@210800z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121073055LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@210830z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121080058LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@210900z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121083114LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@210931z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121090105LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@211001z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121093132LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@211031z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121100119LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@211101z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121103116LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@211131z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1
20191121110123LU8ANB>APRS,TCPIP*,qAS,BM2142POS:@211201z4143.100N/05023.99WrLU8ANB 224.9400/222.3400 CC1