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
20171218090613BD8XZ-9>APGPRS,TCPIP*,qAC,T2EISBERG:@090541h2500.15N/61888>337/001/A=0>9736 Kunming QSO 144.800MHZ 10.23V 18
20171218093140BD8XZ-9>APGPRS,TCPIP*,qAC,T2OSAKA:@093116h2500.56N/31.23.013>316/017/A=0c3654 Kunming QSO 144.800MHZ 10.23V 29
20171218094512BD8XZ-9>APGPRS,TCPIP*,qAC,T2NL:@094438h2500.23N/1108>262/003/A=08886 Kunming QSO 144.800MHZ 10.23V 31
20171218095036BD8XZ-9>APGPRS,TCPIP*,qAC,T2TOKYO3:@095006h2500.21N/10243095A>262/004/A=068847 Kunming QSO 144.800MHZ 10.08V 21
20171218095900BD8XZ-9>APGPRS,TCPIP*,qAC,T2SP:@095SVh35/118>261/009/A=000051 Kunming QSO 144.800MHZ 10.22V 25
20171218101452BD8XZ-9>APGPRS,TCPIP*,qAC,T2DENMARK:@101423h2459.19N/62.78>078/002/A=08721 Kunming QSO 144.800MHZ 10.11V 31
20171218112153BD8XZ-9>APGPRS,TCPIP*,qAC,T2MSSOURI:@112104h2500.22N/32.67>082/009/A=000083 Kunming QSO 144.800MHZ 10.16V 29
20171218112546BD8XZ-9>APGPRS,TCPIP*,qAC,T2NL:@112509h2500.30N/17.77>095/010/A=08394 Kunming QSO 144.800MHZ 10.01V 31