APRS Packet Errors for DB0KS (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
20260209110004DB0KS>APRS,TCPIP*,qAC,T2SPAIN:/091055z4722.85N/01014.47E_198/001g002t037r000p...P...h52b10088LUFFT
20260209120003DB0KS>APRS,TCPIP*,qAC,T2SPAIN:/091155z4722.85N/01014.47E_193/002g002t037r000p...P...h50b10087LUFFT
20260209130003DB0KS>APRS,TCPIP*,qAC,T2POLNW:/091255z4722.85N/01014.47E_069/001g003t033r000p...P...h63b10101LUFFT
20260209140004DB0KS>APRS,TCPIP*,qAC,T2CZECH:/091355z4722.85N/01014.47E_000/000g003t034r000p...P...h65b10097LUFFT
20260209150003DB0KS>APRS,TCPIP*,qAC,T2DENMARK:/091455z4722.85N/01014.47E_123/000g001t035r000p...P...h64b10094LUFFT
20260209160003DB0KS>APRS,TCPIP*,qAC,T2CSNGRAD:/091555z4722.85N/01014.47E_183/003g003t034r000p...P...h65b10095LUFFT