Offline 180.20.143.169:28015 checked 12d ago
crom_rust_test
Connect
srv = rust.server("180.20.143.169: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 18 Sep. 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 62% 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 4, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 7 Oct, 10:40 UTC22d ago | 4 | NaN | running | 0 |
| 1 | Sat 3 Oct, 06:34 UTC27d ago | 4 | held half | 4.2 days | 1 |
# 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
- 180.20.143.169:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Oct 2026, 10:40 UTC
- hostname
- –
- first seen
- 18 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 | 93/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 143/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 39/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 95 on average | 114/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 134/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does crom_rust_test rank?
Player hours over seven days put crom_rust_test at #13,591, in the top 62% of the ranked set.
How many players does crom_rust_test hold at once?
crom_rust_test returns no live count at this refresh, having last been seen 12 days 20 hours ago.
Server facts
Which Rust version is crom_rust_test on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by crom_rust_test. Steam updates your game for you, but the protocol must match to join.
How reliable is crom_rust_test, and is it online now?
Offline now for crom_rust_test, last seen 12 days 20 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 18 September 2026.
In which location is crom_rust_test hosted?
There is no region published for crom_rust_test. 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 180.20.143.169:28015.
Map and rules
Which rules apply on crom_rust_test, and what settings?
No gather rate appears in the name: crom_rust_test. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: 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. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on crom_rust_test?
The game generates the map on crom_rust_test: procedural, size 4,000, seed 179845. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
On what schedule does crom_rust_test wipe?
Too few wipes are on record for crom_rust_test to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 22 days 23 hours ago.
What is wipe day on crom_rust_test like?
Across recent wipes the busiest point averaged 4 players. The crowd on the latest wipe topped out 1 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Lists and tags
Which Rust Data filters and lists contain crom_rust_test?
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.
How should you read the server tags on crom_rust_test?
These tags are published by crom_rust_test and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to crom_rust_test?
The manual route: launch Rust, F1, then client.connect 180.20.143.169:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.