APRS Packet Errors for BD8XZ-9 (last 24 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
20181210002132BD8XZ-9>APGPRS,TCPIP*,qAC,T2GREECE:@002101h2458.793/N5143.318>130/000/A=008482 Kunming QSO 144.800MHZ 09.46V 31
20181210092837BD8XZ-9>APGPRS,TCPIP*,qAC,T2ROMANIA:@092807h2500.05N/2.14>126/000/A=08189 Kunming QSO 144.800MHZ 09.88V 31
20181210093156BD8XZ-9>APGPRS,TCPIP*,qAC,T2ROMANIA:@093119h2500.39N/255>333/014/A=07891 Kunming QSO 144.800MHZ 09.72V 25
20181210094024BD8XZ-9>APGPRS,TCPIP*,qAC,T2SWEDEN2:@094018h2500.45N/10286>245/017/A=000009 Kunming QSO 144.800MHZ 09.60V 25