Offline 50.25.73.37:28015 checked 34d ago
My Local Testing Server
Connect
srv = rust.server("50.25.73.37: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 64% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. 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 22 Sep, 13:28 UTC37d ago | 1 | NaN | running | 1 |
| 1 | Mon 21 Sep, 16:03 UTC38d ago | 1 | NaN | 0.9 days | 1 |
| 2 | Sun 20 Sep, 04:19 UTC40d ago | 1 | NaN | 1.5 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
- 50.25.73.37:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Sep 2026, 13:28 UTC
- hostname
- –
- first seen
- 20 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 · 151 on average | 26/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 52/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 30/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 50/200 |
Quick answers
From the figures on this page.
Player counts
How does My Local Testing Server compare in the rankings?
Player hours over seven days put My Local Testing Server at #14,859, in the top 64% of the ranked set.
How many players does My Local Testing Server hold at once?
Offline now for My Local Testing Server, with the last sample 34 days 2 hours ago.
About the server
What is the Rust version on My Local Testing Server?
The build is Rust network protocol 2633 and build 164530 on Windows, run by My Local Testing Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is My Local Testing Server, and is it up?
The latest sample has My Local Testing Server offline, with a last sighting 34 days 2 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 20 September 2026.
In which location is My Local Testing Server hosted?
No region is published by My Local Testing Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 50.25.73.37:28015 is its address.
Rules, settings, map
What rules and settings are recorded for My Local Testing Server?
No gather rate appears in the name: My Local Testing Server. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. Anti-cheat status: VAC on.
What is the map on My Local Testing Server?
My Local Testing Server runs a procedural map, which the game generates.
Wipe data
When does My Local Testing Server wipe, and how often?
Irregular wipe times on My Local Testing Server leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 37 days 15 hours ago.
What is wipe day on My Local Testing Server like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which Rust Data filters and lists contain My Local Testing Server?
These Rust Data lists include My Local Testing Server: 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.
Which meanings do the tags on My Local Testing Server hold?
Read by the game's server browser, the tags My Local Testing Server publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): The server runs build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^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.
Connecting
How can I connect to My Local Testing Server?
The manual route: launch Rust, F1, then client.connect 50.25.73.37:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.