Online 87.104.253.168:28015 checked 10m ago
Testserver
Connect
srv = rust.server("87.104.253.168: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 23% 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 | Sun 25 Oct, 17:42 UTC4d ago | 1 | NaN | running | 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
- 87.104.253.168:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 17:42 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 | 144/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 197/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 82/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 228/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 351/350 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Testserver rank?
Rank #5,190 on seven-day player hours for Testserver, within the top 23% of all ranked servers.
How many players does Testserver hold at once?
Current row: 0 players on Testserver, against 2 slots. 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 facts
What is the Rust version on Testserver?
Version Rust network protocol 2635 and build 168909 on Linux is reported by Testserver. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Testserver, and is it up?
Testserver reports itself online at the current refresh. Uptime of 58% across the last 3 full days: 42 hours of 72. The first row Rust Data holds for it is dated 25 October 2026.
Where does Testserver sit?
No region is published by Testserver. 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 87.104.253.168:28015.
Map and rules
Which rules apply on Testserver, and what settings?
No gather rate appears in the name: Testserver. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are 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 Testserver selected?
Testserver runs a procedural map, which the game generates.
Wipe data
When does Testserver wipe, and how often?
Too few wipes are on record for Testserver to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 4 days ago.
On Testserver, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Where does Testserver appear among Rust Data lists and filters?
These Rust Data lists include Testserver: 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 Testserver hold?
Read by the game's server browser, the tags Testserver publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to Testserver?
In Rust, F1 opens the console: type client.connect 87.104.253.168:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.