Offline 87.126.24.28:28015 checked 1d ago
Private Test Server
Connect
srv = rust.server("87.126.24.28: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 39% 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 | Thu 22 Oct, 17:58 UTC6d 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
- 87.126.24.28:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 17:58 UTC
- hostname
- –
- first seen
- 22 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 · 157 on average | 109/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 · 116 on average | 133/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 101/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 31/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Private Test Server rank?
Rank #8,595 on seven-day player hours for Private Test Server, within the top 39% of all ranked servers.
How full does Private Test Server run?
Offline now for Private Test Server, with the last sample 25 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 19:00 UTC is the busiest, at 1 players.
Server data
Which Rust version is Private Test Server on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Private Test Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is Private Test Server, and is it online now?
The latest sample has Private Test Server offline, with a last sighting 25 hours ago. Uptime of 8% across the last 5 full days: 9 hours of 120. The first row Rust Data holds for it is dated 22 October 2026.
Which location does Private Test Server run from?
For Private Test Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 87.126.24.28:28015 is its address.
Rules, settings, map
Which rules apply on Private Test Server, and what settings?
The name Private Test Server carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. 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 off.
Which map has Private Test Server loaded?
The game generates its map: procedural, on Private Test Server.
Wipe data
When does Private Test Server wipe, and on what schedule?
The record for Private Test Server holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 6 days 3 hours ago.
On Private Test Server, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 1 hours in.
Tags and filters
Where does Private Test Server appear among Rust Data lists and filters?
On Rust Data, Private Test Server appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on Private Test Server hold?
Read by the game's server browser, the tags Private Test Server publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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 Private Test Server?
The manual route: launch Rust, F1, then client.connect 87.126.24.28:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.