APRS Packet Errors for HS1UQO-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
20260208151908	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@151908h1543.49N/10006.94ErAPRS-IS for Win32
20260208154909	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@154908h1543.49N/10006.94ErAPRS-IS for Win32
20260208161909	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@161909h1543.49N/10006.94ErAPRS-IS for Win32
20260208164909	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@164909h1543.49N/10006.94ErAPRS-IS for Win32
20260208171910	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@171909h1543.49N/10006.94ErAPRS-IS for Win32
20260208174910	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@174910h1543.49N/10006.94ErAPRS-IS for Win32
20260208181910	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@181910h1543.49N/10006.94ErAPRS-IS for Win32
20260208184911	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@184910h1543.49N/10006.94ErAPRS-IS for Win32
20260208191911	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@191911h1543.49N/10006.94ErAPRS-IS for Win32
20260208194911	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@194911h1543.49N/10006.94ErAPRS-IS for Win32
20260208201912	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@201911h1543.49N/10006.94ErAPRS-IS for Win32
20260208204912	HS1UQO-10>APWW11,TCPIP*,qAC,T2UKRAINE:@204912h1543.49N/10006.94ErAPRS-IS for Win32