APRS Packet Errors for YE1BPQ-2 (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
20260208145116YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208152138YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208155200YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208162222YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208165244YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208172307YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208175328YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208182350YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208185411YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208192434YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208195456YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260208202518YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi