Offline 153.177.71.237:28015 checked 3d ago
crom_rust_test
Connect
srv = rust.server("153.177.71.237: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, measured since 23 Oct. 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 bestTop 53% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 15:22 UTC5d ago | 1 | NaN | running | 0 |
# 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
4000 · seed 179845
- map
- Procedural Map
- size
- 4000
- seed
- 179845
Server
srv.info()- address
- 153.177.71.237:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Oct 2026, 10:40 UTC
- hostname
- –
- first seen
- 21 Oct 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 · 156 on average | 211/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 177/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 89 on average | 136/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 52/1000 |
Quick answers
From the figures on this page.
Population
How does crom_rust_test compare in the rankings?
Over the last seven days crom_rust_test sits at #11,826 on player hours, in the top 53% of ranked servers.
How many players does crom_rust_test hold at once?
The current row shows crom_rust_test offline; the last response was 3 days 4 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
Which Rust version is crom_rust_test on?
Rust network protocol 2635 and build 168909 on Windows is what crom_rust_test runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is crom_rust_test, and is it up?
crom_rust_test is offline at this refresh; the last response came 3 days 4 hours ago. 4 of 144 hours up over the last 6 full days, or 3%. Its earliest recorded date in Rust Data is 21 October 2026.
Which location does crom_rust_test run from?
For crom_rust_test, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 153.177.71.237:28015.
Rules, settings, map
What rules and settings are recorded for crom_rust_test?
The name crom_rust_test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on crom_rust_test?
crom_rust_test runs a procedural map of size 4,000 with seed 179845, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does crom_rust_test wipe, and on what schedule?
A rhythm cannot be read from the wipes of crom_rust_test on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 21 days 5 hours ago, and that is the one in play.
On crom_rust_test, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Where does crom_rust_test appear among Rust Data lists and filters?
These Rust Data lists include crom_rust_test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on crom_rust_test hold?
The game's server browser reads these tags from crom_rust_test: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join crom_rust_test?
Enter client.connect 153.177.71.237:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.