[Bacardi]

...to clarify also, rate, cl_cmdrate, cl_updaterate are client side console variables.
Means, these just hold value, what you set in your own game.
- Means, you should not follow/check clients cvar values.

*seems game now change cvar value when you join in server as well.
But it revert values back when you disconnect from server.

] cl_updaterate 
"cl_updaterate" = "66" ( def. "20" )
** NOTE: The real value is 10.000 but the server has temporarily restricted it to 66.000 **
 archive notconnected
 - Number of packets per second of updates you are requesting from the server
] cl_cmdrate 
"cl_cmdrate" = "66" ( def. "30" ) min. 10.000000 max. 100.000000
** NOTE: The real value is 10.000 but the server has temporarily restricted it to 66.000 **
 archive
 - Max number of command packets sent to server per second
] rate
"rate" = "66000" ( def. "80000" )
** NOTE: The real value is 3500.000 but the server has temporarily restricted it to 66000.000 **
 archive
 - Max bytes/sec the host can receive data

Another thing, even today in cs:s, game default values comes mostly from from HL2 game,
which are very low values and for singlegame play.

Back in day of cs:s era, people wrote a lot of recommended rate settings for cs:s in web sites, but those were mostly for HL1 mod Counter-Strike.
For example rate 24000, cl_upraterate 100, cl_cmdrate 100
- which is very low rate for high update rate. Players made CHOKE for themself.
- 66 tickrate is now default speed.

Then there was old calculator which people looked even today
http://web.archive.org/web/202111290.../drekrates.php
- This give also wrong answers.


But, for reduce lag with higher count of players:
- Better decrease updaterate and set rate very high.

for min. rate setting is 1000 x updaterate, this depend how well map is made and player count.

This is my (shame) calculator, I practised java script and html few years ago
ambaca.github.io/rate-calculator-2015/

But calculations are very simple. And you need look net_graph 5 from in game.