Offline 46.53.173.145:28015 checked 14h ago
My Staging Test
Connect
srv = rust.server("46.53.173.145: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 best
Top 44% 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 | Tue 27 Oct, 16:58 UTC14h ago | NaN | NaN | running | 1 |
| 1 | Thu 22 Oct, 15:05 UTC5d ago | 1 | held half | 5.1 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 46.53.173.145:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 16:58 UTC
- hostname
- –
- first seen
- 22 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 536 on average | 383/350 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 200/225 |
| 2 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 318 on average | 21/250 |
| 3 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 317 on average | 27/250 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 276 on average | 101/225 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 265 on average | 38/100 |
Quick answers
From the figures on this page.
Player counts
How does My Staging Test compare in the rankings?
Player hours over seven days put My Staging Test at #9,746, in the top 44% of the ranked set.
How full does My Staging Test run?
Offline now for My Staging Test, with the last sample 14 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Peak hour in the last 48 hours: 17:00 UTC, mean 1 players.
About the server
What Rust version does My Staging Test run?
Rust network protocol 2635 and build 169364 on Windows is what My Staging Test runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is My Staging Test, and is it up?
My Staging Test is offline at this refresh; the last response came 14 hours ago. Over the last 5 full days the hours up number 3 of 120, 2%. The first row Rust Data holds for it is dated 22 October 2026.
Where does My Staging Test sit?
There is no region published for My Staging Test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 46.53.173.145:28015 is its address.
Map and rules
What rules and settings are recorded for My Staging Test?
You will not find a gather rate in the string My Staging Test. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Which map has My Staging Test loaded?
The game generates its map: procedural, on My Staging Test.
Wipe data
When does My Staging Test wipe, and on what schedule?
A rhythm cannot be read from the wipes of My Staging 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. This world was created 14 hours ago.
On My Staging Test, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. 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 My Staging Test?
These Rust Data lists include My Staging Test: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours.
How should you read the server tags on My Staging Test?
Read by the game's server browser, the tags My Staging Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs169364 (Build): The server runs build 169364; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. 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 My Staging Test?
The manual route: launch Rust, F1, then client.connect 46.53.173.145:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.