Offline 95.105.86.187:28505 checked 3d ago
Menu Plugin Test Server
Connect
srv = rust.server("95.105.86.187:28506")
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 47% 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 | Mon 26 Oct, 14:01 UTC3d ago | 1 | 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
- 95.105.86.187:28505
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 14:01 UTC
- hostname
- –
- first seen
- 25 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 · 151 on average | 67/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 114/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 29/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 95 on average | 96/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 92/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Menu Plugin Test Server rank?
Over the last seven days Menu Plugin Test Server sits at #10,354 on player hours, in the top 47% of ranked servers.
What population does Menu Plugin Test Server carry?
Menu Plugin Test Server returns no live count at this refresh, having last been seen 3 days 14 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server facts
What Rust version does Menu Plugin Test Server run?
Rust network protocol 2635 and build 168909 on Windows is what Menu Plugin Test Server runs. Joining needs the same protocol on your game; Steam handles the update.
Is Menu Plugin Test Server up, and what does its uptime show?
Menu Plugin Test Server is offline at this refresh; the last response came 3 days 14 hours ago. 4 of 96 hours up over the last 4 full days, or 4%. Rust Data logged it first on 25 October 2026.
Where does Menu Plugin Test Server sit?
There is no region published for Menu Plugin Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 95.105.86.187:28505 is its address.
Rules, settings, map
Which rules apply on Menu Plugin Test Server, and what settings?
No gather rate appears in the name: Menu Plugin Test Server. No custom cap; the default of 8 players per group stands. 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. The VAC field reads off.
What is the map on Menu Plugin Test Server?
Menu Plugin Test Server runs a procedural map, which the game generates.
Wipe schedule
When does Menu Plugin Test Server wipe, and how often?
Too few wipes are on record for Menu Plugin Test Server 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. The world it runs now was generated 3 days 18 hours ago.
On Menu Plugin Test Server, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which lists on Rust Data hold Menu Plugin Test Server, and which filters?
The Rust Data lists that Menu Plugin Test Server fits are: 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.
How should you read the server tags on Menu Plugin Test Server?
Read by the game's server browser, the tags Menu Plugin Test 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; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $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. 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.
How to join
How can I connect to Menu Plugin Test Server?
In Rust, F1 opens the console: type client.connect 95.105.86.187:28505. Launch Rust on this page does the same by opening the game through Steam and connecting.