Offline 50.46.161.24:28015 checked 5d ago
Rust-in-Rust dev
Connect
srv = rust.server("50.46.161.24: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 69% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 00:07 UTC6d ago | 0 | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 50.46.161.24:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 00:07 UTC
- hostname
- –
- first seen
- 23 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 · 150 on average | 16/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 30/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 8/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 37/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 158/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Rust-in-Rust dev rank?
Player hours over seven days put Rust-in-Rust dev at #15,284, in the top 69% of the ranked set.
How full does Rust-in-Rust dev run?
Rust-in-Rust dev returns no live count at this refresh, having last been seen 5 days 7 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is Rust-in-Rust dev on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Rust-in-Rust dev. The protocol has to match before you can join, and Steam does the updating.
How reliable is Rust-in-Rust dev, and is it online now?
Offline now for Rust-in-Rust dev, last seen 5 days 7 hours ago. Uptime of 12% across the last 6 full days: 18 hours of 144. Its earliest recorded date in Rust Data is 23 October 2026.
In which location is Rust-in-Rust dev hosted?
There is no region published for Rust-in-Rust dev. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 50.46.161.24:28015 is its address.
Map and rules
Which settings and rules does Rust-in-Rust dev run?
You will not find a gather rate in the string Rust-in-Rust dev. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has Rust-in-Rust dev loaded?
The game generates its map: procedural, on Rust-in-Rust dev.
Wipe schedule
When does Rust-in-Rust dev wipe, and on what schedule?
Too few wipes are on record for Rust-in-Rust dev 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. A new world was started 6 days 1 hours ago, and that is the one in play.
On Rust-in-Rust dev, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Where does Rust-in-Rust dev appear among Rust Data lists and filters?
These Rust Data lists include Rust-in-Rust dev: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on Rust-in-Rust dev hold?
These tags are published by Rust-in-Rust dev and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. 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
What is the way into Rust-in-Rust dev?
In Rust, F1 opens the console: type client.connect 50.46.161.24:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.