Offline 174.164.33.204:28015 checked 32d ago
rust_240hz_bench
Connect
srv = rust.server("174.164.33.204:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 174.164.33.204:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Sep 2026, 09:02 UTC
- hostname
- –
- first seen
- 27 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 38/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 74/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 30/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 77/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 296/310 |
Quick answers
From the figures on this page.
Population
What position does rust_240hz_bench take in the server rankings?
Player hours over seven days put rust_240hz_bench at #16,957, in the top 71% of the ranked set.
How full does rust_240hz_bench run?
The current row shows rust_240hz_bench offline; the last response was 32 days 2 hours ago.
About the server
What is the Rust version on rust_240hz_bench?
Version Rust network protocol 2633 and build 165217 on Windows is reported by rust_240hz_bench. The protocol has to match before you can join, and Steam does the updating.
How reliable is rust_240hz_bench, and is it online now?
rust_240hz_bench is offline at this refresh; the last response came 32 days 2 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 27 September 2026.
In which location is rust_240hz_bench hosted?
There is no region published for rust_240hz_bench. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 174.164.33.204:28015.
Map and rules
Which rules apply on rust_240hz_bench, and what settings?
No gather rate appears in the name: rust_240hz_bench. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC is not running; Valve's anti-cheat is off.
Which map has rust_240hz_bench selected?
The game generates its map: procedural, on rust_240hz_bench.
Wipes and dates
When does rust_240hz_bench wipe, and how often?
A rhythm cannot be read from the wipes of rust_240hz_bench on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 32 days 13 hours ago.
Lists and tags
Which Rust Data filters and lists contain rust_240hz_bench?
On Rust Data, rust_240hz_bench appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on rust_240hz_bench?
The game's server browser reads these tags from rust_240hz_bench: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into rust_240hz_bench?
The manual route: launch Rust, F1, then client.connect 174.164.33.204:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.