APRS Packet Errors for BG5JQQ (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
20260208150003BG5JQQ>APRS,TCPIP*,qAC,T2HK:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208153103BG5JQQ>APRS,TCPIP*,qAC,T2TAIPEI:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208160004BG5JQQ>APRS,TCPIP*,qAC,T2TOKYO:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208163103BG5JQQ>APRS,TCPIP*,qAC,T2HK:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208170003BG5JQQ>APRS,TCPIP*,qAC,T2OSAKA:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208173105BG5JQQ>APRS,TCPIP*,qAC,T2FUKUOKA:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208180003BG5JQQ>APRS,TCPIP*,qAC,T2FUKUOKA:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208183103BG5JQQ>APRS,TCPIP*,qAC,T2TAIPEI:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208190004BG5JQQ>APRS,TCPIP*,qAC,T2HK:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208193105BG5JQQ>APRS,TCPIP*,qAC,T2TAIWAN:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208200002BG5JQQ>APRS,TCPIP*,qAC,T2HAKATA:!3008.18N/12119.58E>APRS BY Python FROM JiangXi
20260208203103BG5JQQ>APRS,TCPIP*,qAC,T2HAKATA:!3008.18N/12119.58E>APRS BY Python FROM JiangXi