APRS Packet Errors for AK4B (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
20260208150330AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@144646h3410.90N/08651.61WyAPRS-IS for Win32
20260208153331AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@151647h3410.90N/08651.61WyAPRS-IS for Win32
20260208160331AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@154647h3410.90N/08651.61WyAPRS-IS for Win32
20260208163332AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@161648h3410.90N/08651.61WyAPRS-IS for Win32
20260208170332AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@164648h3410.90N/08651.61WyAPRS-IS for Win32
20260208173332AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@171648h3410.90N/08651.61WyAPRS-IS for Win32
20260208180333AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@174648h3410.90N/08651.61WyAPRS-IS for Win32
20260208183333AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@181649h3410.90N/08651.61WyAPRS-IS for Win32
20260208190333AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@184649h3410.90N/08651.61WyAPRS-IS for Win32
20260208193333AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@191649h3410.90N/08651.61WyAPRS-IS for Win32
20260208200334AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@194650h3410.90N/08651.61WyAPRS-IS for Win32
20260208203342AK4B>APWW10,TCPIP*,qAC,T2DENMARK:@201657h3410.90N/08651.61WyAPRS-IS for Win32