Offline 91.152.86.210:28015 checked 5d ago
MyTestServer
Connect
srv = rust.server("91.152.86.210: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 bestTop 43% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 19 Oct, 10:28 UTC8d 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
- 91.152.86.210:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 10:51 UTC
- hostname
- –
- first seen
- 19 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 · 160 on average | 40/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 48/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 18/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 7/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does MyTestServer rank?
Over the last seven days MyTestServer sits at #9,673 on player hours, in the top 43% of ranked servers.
How full does MyTestServer run?
MyTestServer returns no live count at this refresh, having last been seen 5 days 9 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server facts
What Rust version does MyTestServer run?
The build is Rust network protocol 2634 and build 167781 on Windows, run by MyTestServer. Steam updates your game for you, but the protocol must match to join.
How reliable is MyTestServer, and is it online now?
MyTestServer is offline at this refresh; the last response came 5 days 9 hours ago. Over the last 7 full days the hours up number 9 of 168, 5%. Rust Data logged it first on 19 October 2026.
In which location is MyTestServer hosted?
No region is published by MyTestServer. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 91.152.86.210:28015.
Settings and map
What rules and settings are recorded for MyTestServer?
The name MyTestServer carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has MyTestServer selected?
The game generates its map: procedural, on MyTestServer.
Wipe schedule
On what schedule does MyTestServer wipe?
Too few wipes are on record for MyTestServer to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 8 days 16 hours ago.
What is wipe day on MyTestServer like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in.
Tags and filters
Where does MyTestServer appear among Rust Data lists and filters?
On Rust Data, MyTestServer appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on MyTestServer?
These tags are published by MyTestServer and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into MyTestServer?
In Rust, F1 opens the console: type client.connect 91.152.86.210:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.