Offline 37.186.121.127:28015 checked 18d ago
TEST SERVER NAME
Connect
srv = rust.server("37.186.121.127:28015")
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 71% 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 | Sat 3 Oct, 11:30 UTC26d ago | 1 | NaN | running | 0 |
| 1 | Fri 2 Oct, 20:22 UTC27d ago | 1 | NaN | 0.6 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
- 37.186.121.127:28015
- region
- –
- max players
- 10
- group limit
- not published
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 11:30 UTC
- hostname
- –
- first seen
- 30 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 | 81/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 144/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 55/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 91 on average | 141/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Player counts
What position does TEST SERVER NAME take in the server rankings?
Over the last seven days TEST SERVER NAME sits at #15,750 on player hours, in the top 71% of ranked servers.
What population does TEST SERVER NAME carry?
TEST SERVER NAME returns no live count at this refresh, having last been seen 18 days 1 hours ago.
About the server
Which Rust version is TEST SERVER NAME on?
Version Rust network protocol 2332 on Windows is reported by TEST SERVER NAME. Steam updates your game for you, but the protocol must match to join.
Is TEST SERVER NAME up, and what does its uptime show?
The latest sample has TEST SERVER NAME offline, with a last sighting 18 days 1 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 30 September 2026.
Where does TEST SERVER NAME sit?
No region is published by TEST SERVER NAME. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 37.186.121.127:28015 is its address.
Rules, settings, map
What rules and settings are recorded for TEST SERVER NAME?
The name TEST SERVER NAME carries no gather rate. Group limits do not appear in its data. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Anti-cheat status: VAC off.
Which map has TEST SERVER NAME selected?
TEST SERVER NAME runs a procedural map, which the game generates.
Wipes and dates
On what schedule does TEST SERVER NAME wipe?
Too few wipes are on record for TEST SERVER NAME 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. This world was created 26 days 8 hours ago.
On TEST SERVER NAME, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which lists on Rust Data hold TEST SERVER NAME, and which filters?
The Rust Data lists that TEST SERVER NAME fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded.
How should you read the server tags on TEST SERVER NAME?
The game's server browser reads these tags from TEST SERVER NAME: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; v2332 (Protocol): To join, your game must run protocol 2332; ptrak (Networking): Standard network layer for Rust: RakNet; oxide (Oxide): Plugin framework: Oxide (uMod); modded (Modded): The Modded section lists it, because plugins or settings change the game; h955eb6e7 (Custom tag): A plugin or the owner added this; standard Rust does not define it; stok (Custom tag): A plugin or the owner added this; standard Rust does not define it. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to TEST SERVER NAME?
The manual route: launch Rust, F1, then client.connect 37.186.121.127:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.