APRS Packet Errors for YC2YEK-10 (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
20260208152850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208155850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208162850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208165850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208172850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208175850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208182850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208185850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208192850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208195850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208202850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman
20260208205850YC2YEK-10>APDW17,TCPIP*,qAC,T2JKTP:!0744.55SG11013.45E&iGate Sendangmulyo Minggir Sleman