Offline 46.147.132.247:28015 checked 19d ago
My Staging Test Server
Connect
srv = rust.server("46.147.132.247:28016")
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 bestTop 72% 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, 21 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 17:36 UTC20d 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
- 46.147.132.247:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 17:36 UTC
- hostname
- –
- first seen
- 28 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 · 149 on average | 163/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 68/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 12/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 18/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does My Staging Test Server rank?
Rank #15,863 on seven-day player hours for My Staging Test Server, within the top 72% of all ranked servers.
What population does My Staging Test Server carry?
My Staging Test Server returns no live count at this refresh, having last been seen 19 days 21 hours ago.
Server data
What is the Rust version on My Staging Test Server?
Version Rust network protocol 2635 and build 167443 on Windows is reported by My Staging Test Server. Joining needs the same protocol on your game; Steam handles the update.
Is My Staging Test Server up, and what does its uptime show?
The latest sample has My Staging Test Server offline, with a last sighting 19 days 21 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 28 September 2026.
Which location does My Staging Test Server run from?
There is no region published for My Staging Test Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 46.147.132.247:28015 is its address.
Settings and map
Which settings and rules does My Staging Test Server run?
You will not find a gather rate in the string My Staging Test Server. 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. 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.
What is the map on My Staging Test Server?
My Staging Test Server runs a procedural map, which the game generates.
Wipe schedule
When does My Staging Test Server wipe, and on what schedule?
A rhythm cannot be read from the wipes of My Staging Test Server 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 20 days 18 hours ago.
On My Staging Test Server, what happens on wipe day?
The average peak over recent wipes is 0 players. 21 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold My Staging Test Server, and which filters?
On Rust Data, My Staging Test Server appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on My Staging Test Server hold?
Read by the game's server browser, the tags My Staging Test Server publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs167443 (Build): Build number: 167443; 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): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into My Staging Test Server?
Enter client.connect 46.147.132.247:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.