APRS Packet Errors for ub3tbw-LS (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
20260311173000	ub3tbw-LS>APRRDZ,TCPIP,qAC,T2RUSSIA2:;H1411545 000008h0000.00N/00000.00EO!w!!!Clb=0.0m/s t=24.5C h=46.6% 403.000MHz Type=MP3HS rdzTTGOsonde
20260311173020	ub3tbw-LS>APRRDZ,TCPIP,qAC,T2RUSSIA2:;H1411545 000028h0000.00N/00000.00EO!w!!!Clb=0.0m/s t=23.9C h=46.0% 403.000MHz Type=MP3HS rdzTTGOsonde
20260311175438	ub3tbw-LS>APRRDZ,TCPIP,qAC,T2RUSSIA2:;H1411545 235942h0000.00N/00000.00EO!w!!!Clb=0.0m/s t=25.0C h=47.0% 403.000MHz Type=MP3HS rdzTTGOsonde
20260311175501	ub3tbw-LS>APRRDZ,TCPIP,qAC,T2RUSSIA2:;H1411545 000004h0000.00N/00000.00EO!w!!!Clb=0.0m/s t=25.2C h=46.0% 403.000MHz Type=MP3HS rdzTTGOsonde
20260311175522	ub3tbw-LS>APRRDZ,TCPIP,qAC,T2RUSSIA2:;H1411545 000026h0000.00N/00000.00EO!w!!!Clb=0.0m/s t=23.9C h=43.2% 403.000MHz Type=MP3HS rdzTTGOsonde
20260311175543	ub3tbw-LS>APRRDZ,TCPIP,qAC,T2RUSSIA2:;H1411545 000046h0000.00N/00000.00EO!w!!!Clb=0.0m/s t=18.5C h=43.7% 403.000MHz Type=MP3HS rdzTTGOsonde