APRS Packet Errors for TA2KRE-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
20260208200247TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@200028h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260208203247TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@203028h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260208210225TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@210002h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260208213225TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@213002h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260208220225TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@220002h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260208223225TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@223002h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260208230225TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@230002h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260208233226TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@233003h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260209000228TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@000003h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260209003226TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@003003h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260209010227TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@010004h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE
20260209013227TA2KRE-10>APWW11,TCPIP*,qAC,T2BELGIUM:@013004h3950.81N/03330.28E-IGATE-KITRAD KIRIKKALE