APRS Packet Errors for YG2BMY-1 (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
20251104102648YG2BMY-1>AESPG4,TCPIP*,qAC,T2OSAKA:=657.21S/11042.05E_DEMAK WEATHER STATION
20251104102924YG2BMY-1>AESPG4,TCPIP*,qAC,T2OSAKA:=657.21S/11042.05E_DEMAK WEATHER STATION
20251104103323YG2BMY-1>AESPG4,TCPIP*,qAC,T2TAIPEI:=657.21S/11042.05E_DEMAK WEATHER STATION
20251104112200YG2BMY-1>AESPG4,TCPIP*,qAC,T2OSAKA:=657.21S/11042.05E_DEMAK WS
20251104112629YG2BMY-1>AESPG4,TCPIP*,qAC,T2OSAKA:=657.21S/11042.05E_DEMAK WS
20251104113151YG2BMY-1>AESPG4,TCPIP*,qAC,T2OSAKA:=657.21S/11042.05E_DEMAK WS
20251104113555YG2BMY-1>AESPG4,TCPIP*,qAC,T2CSNGRAD:=657.21S/11042.05E_DEMAK WS
20251104114119YG2BMY-1>AESPG4,TCPIP*,qAC,T2CSNGRAD:=657.21S/11042.05E_DEMAK WS
20251104114441YG2BMY-1>AESPG4,TCPIP*,qAC,T2TAIPEI:=657.21S/11042.04E_DEMAK WS
20251104114627YG2BMY-1>AESPG4,TCPIP*,qAC,T2YANTAI:=657.21S/11042.04E_DEMAK WS
20251104115152YG2BMY-1>AESPG4,TCPIP*,qAC,T2YANTAI:=657.21S/11042.04E_DEMAK WS
20251104115510YG2BMY-1>AESPG4,TCPIP*,qAC,T2HK:=657.21S/11042.04E_DEMAK WS
20251104120428YG2BMY-1>AESPG4,TCPIP*,qAC,T2HAKATA:=657.21S/11042.04E_DEMAK WS
20251104121030YG2BMY-1>AESPG4,TCPIP*,qAC,T2TAIWAN:=657.21S/11042.04E_DEMAK WS
20251104121155YG2BMY-1>AESPG4,TCPIP*,qAC,T2HAKATA:=657.21S/11042.04E_DEMAK WS