Online 115.162.109.10:28015 checked 11m ago
MyTestServer
Connect
srv = rust.server("115.162.109.10: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 21% 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 | Fri 2 Oct, 12:43 UTC26d 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
- 115.162.109.10:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 12:43 UTC
- hostname
- –
- first seen
- 13 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 · 149 on average | 163/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 184/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 75/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 16/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 22/1000 |
Quick answers
From the figures on this page.
Population data
What position does MyTestServer take in the server rankings?
Rank #4,626 on seven-day player hours for MyTestServer, within the top 21% of all ranked servers.
What population does MyTestServer carry?
Current row: 1 players on MyTestServer, against 5 slots. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 14:00 UTC, averaging 1 players.
Server facts
What Rust version does MyTestServer run?
Rust network protocol 2635 and build 168909 on Windows is what MyTestServer runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is MyTestServer, and is it up?
MyTestServer reports itself online at the current refresh. Over the last 7 full days the hours up number 97 of 168, 58%. Rust Data logged it first on 13 September 2026.
In which location is MyTestServer hosted?
For MyTestServer, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 115.162.109.10:28015.
Map and rules
Which rules apply on MyTestServer, and what settings?
No gather rate appears in the name: MyTestServer. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on MyTestServer?
The game generates its map: procedural, on MyTestServer.
Wipe data
On what schedule does MyTestServer wipe?
A rhythm cannot be read from the wipes of MyTestServer 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 26 days 23 hours ago.
On MyTestServer, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 1 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which lists on Rust Data hold MyTestServer, and which 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.
Which meanings do the tags on MyTestServer hold?
Read by the game's server browser, the tags MyTestServer publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Join steps
How can I connect to MyTestServer?
The manual route: launch Rust, F1, then client.connect 115.162.109.10:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.