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
20171020092838BD8XZ-9>APGPRS,TCPIP*,qAC,T2CAEAST:@092801h2500.54N/17>150/000/A=0B9077 Kunming QSO 144.800MHZ 09.42V 31
20171020093321BD8XZ-9>APGPRS,TCPIP*,qAC,T2CAEAST:@093245h2500.55N/20>142/000/A=071051 Kunming QSO 144.800MHZ 09.26V 31
20171020094736BD8XZ-9>APGPRS,TCPIP*,qAC,T2CAEAST:@094710h2500.244/2920>250/00A/A=08394 Kunming QSO 144.800MHZ 09.05V 26
20171020095006BD8XZ-9>APGPRS,TCPIP*,qAC,T2SAPPORO:@094930h2500.23N/1816>140/000/A=08394 Kunming QSO 144.800MHZ 08.75V 20
20171020101030BD8XZ-9>APGPRS,TCPIP*,qAC,T2CAEAST:@101000h2459.73N/43>198/016/A=000074 Kunming QSO 144.800MHZ 08.75V 26
20171020101526BD8XZ-9>APGPRS,TCPIP*,qAC,T2CAEAST:@101455h2459.21N/28541.724>103/010/A=006614 Kunming QSO 144.800MHZ 08.65V 21