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
20250314170608	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314173609	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314180610	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314183611	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314190612	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314193613	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314200614	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314203615	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314210616	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314213617	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314220618	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/
20250314223619	JH1LWU-13>APX221,TCPIP*,qAC,T2OSAKA:=/