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
20260209130833YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209133855YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209140917YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209143940YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209151002YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209154024YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209161046YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209164108YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209171130YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209174152YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209181214YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi
20260209184236YE1BPQ-2>AESPG4,TCPIP*,qAC,T2TOKYO:=0657.86S/10656.27E#APRS Igate Sukabumi