Offline 95.26.138.210:28015 checked 18d ago
Testing server
Connect
srv = rust.server("95.26.138.210:28016")
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 61% 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 | Fri 9 Oct, 19:18 UTC18d 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 95.26.138.210:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 19:18 UTC
- hostname
- –
- first seen
- 9 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 | 39/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 47/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
Against other Rust servers, how does Testing server rank?
Player hours over seven days put Testing server at #13,578, in the top 61% of the ranked set.
How many players does Testing server hold at once?
Testing server returns no live count at this refresh, having last been seen 18 days 3 hours ago.
Server facts
What Rust version does Testing server run?
The build is Rust network protocol 2634 and build 167398 on Windows, run by Testing server. The protocol has to match before you can join, and Steam does the updating.
Is Testing server up, and what does its uptime show?
Offline now for Testing server, last seen 18 days 3 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 9 October 2026.
Where does Testing server sit?
There is no region published for Testing server. 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 95.26.138.210:28015.
Settings and map
What rules and settings are recorded for Testing server?
No gather rate appears in the name: Testing server. 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. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Wipes and dates
When does Testing server wipe, and how often?
A rhythm cannot be read from the wipes of Testing server 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. A new world was started 18 days 8 hours ago, and that is the one in play.
On Testing server, what happens on wipe day?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain Testing server?
These Rust Data lists include Testing server: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Testing server?
Read by the game's server browser, the tags Testing server publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): Build number: 167398; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to Testing server?
In Rust, F1 opens the console: type client.connect 95.26.138.210:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.