APRS Packet Errors for BD8XZ-9 (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
20191117085351BD8XZ-9>APGPRS,TCPIP*,qAC,T2CAWEST:@085325h2501.11N/18242.90K>334/003/A=0I8481 Kunming QSO 144.800MHZ 09.21V 26
20191117100901BD8XZ-9>APGPRS,TCPIP*,qAC,T2BELGIUM:@100842h2501.577/M5.62>162/022/A=000090 Kunming QSO 144.800MHZ 09.51V 30
20191117103035BD8XZ-9>APGPRS,TCPIP*,qAC,T2MAZURY:@102959h2458.90N/39241.992>100/000/A=010222 Kunming QSO 144.800MHZ 08.86V 31
20191117104610BD8XZ-9>APGPRS,TCPIP*,qAC,T2VAN:@104554h2500.60N/.4.37>306/011/A=05762 Kunming QSO 144.800MHZ 08.73V 31
20191117123421BD8XZ-9>APGPRS,TCPIP*,qAC,T2TURKEY:@123405h2500.45N/2468>095/000/A=000000 Kunming QSO 144.800MHZ 08.89V 31
20191117123828BD8XZ-9>APGPRS,TCPIP*,qAC,T2EHIME:@123810h2500.27N/26240.858>230/022/A=0m1486 Kunming QSO 144.800MHZ 08.64V 23
20191117125320BD8XZ-9>APGPRS,TCPIP*,qAC,T2BELGIUM:@125257h2458.70N/N3>273/013/A=000028 Kunming QSO 144.800MHZ 08.73V 27