Offline 88.230.56.225:28015 checked 21d ago
Berke Test Server
Connect
srv = rust.server("88.230.56.225: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 72% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 10:24 UTC21d ago | 0 | 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
- 88.230.56.225:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 10:24 UTC
- hostname
- –
- first seen
- 8 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 | 113/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 72/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 208/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 349/350 |
Quick answers
From the figures on this page.
Player counts
How does Berke Test Server compare in the rankings?
Rank #15,886 on seven-day player hours for Berke Test Server, within the top 72% of all ranked servers.
How many players does Berke Test Server hold at once?
Offline now for Berke Test Server, with the last sample 21 days 7 hours ago.
Server facts
What is the Rust version on Berke Test Server?
The build is Rust network protocol 2634 and build 167231 on Windows, run by Berke Test Server. Steam updates your game for you, but the protocol must match to join.
How reliable is Berke Test Server, and is it online now?
Berke Test Server is offline at this refresh; the last response came 21 days 7 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 8 October 2026.
Which location does Berke Test Server run from?
No region is published by Berke Test 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 88.230.56.225:28015.
Map and rules
What rules and settings are recorded for Berke Test Server?
No gather rate appears in the name: Berke Test Server. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has Berke Test Server loaded?
Berke Test Server runs a procedural map, which the game generates.
Wipes and dates
On what schedule does Berke Test Server wipe?
The record for Berke Test Server holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 21 days 8 hours ago.
On Berke Test Server, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which Rust Data filters and lists contain Berke Test Server?
The Rust Data lists that Berke Test Server fits are: 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 Berke Test Server?
The game's server browser reads these tags from Berke Test Server: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167231 (Build): Recorded game build: 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into Berke Test Server?
In Rust, F1 opens the console: type client.connect 88.230.56.225:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.