APRS Packet Errors for JH1LWU-13 (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
20260208181052JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_339/000g000t027h43b10080XU2k
20260208184053JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_342/000g000t026h44b10070XU2k
20260208191054JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_336/000g000t025h47b10100XU2k
20260208194055JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_345/000g000t027h44b10080XU2k
20260208201056JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_332/000g000t027h41b10080XU2k
20260208204057JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_333/000g000t028h39b10100XU2k
20260208211058JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_115/000g002t028h40b10080XU2k
20260208214059JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_146/000g001t028h40b10120XU2k
20260208221100JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_359/000g000t029h39b10080XU2k
20260208224101JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_024/000g000t032h36b10120XU2k
20260208231102JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_024/000g002t036h30b10120XU2k
20260208234103JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=3546.56N/13954.32E_297/000g002t039h27b10120XU2k