Offline 93.217.225.233:28015 checked 3d ago
KTest
Connect
srv = rust.server("93.217.225.233: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 best
Top 32% 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 | Sat 24 Oct, 13:56 UTC4d ago | 1 | NaN | running | 1 |
| 1 | Wed 21 Oct, 10:09 UTC7d ago | 1 | held half | 3.2 days | 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
- 93.217.225.233:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 13:56 UTC
- hostname
- –
- first seen
- 18 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 · 156 on average | 47/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 44/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 51/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6/1000 |
Quick answers
From the figures on this page.
Population
How does KTest compare in the rankings?
Over the last seven days KTest sits at #7,021 on player hours, in the top 32% of ranked servers.
What population does KTest carry?
Offline now for KTest, with the last sample 3 days 8 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server data
What Rust version does KTest run?
Rust network protocol 2635 and build 168909 on Windows is what KTest runs. The protocol has to match before you can join, and Steam does the updating.
Is KTest up, and what does its uptime show?
KTest is offline at this refresh; the last response came 3 days 8 hours ago. Uptime of 15% across the last 7 full days: 26 hours of 168. The first row Rust Data holds for it is dated 18 October 2026.
Where does KTest sit?
No region is published by KTest. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 93.217.225.233:28015.
Rules, settings, map
Which settings and rules does KTest run?
You will not find a gather rate in the string KTest. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on KTest?
KTest runs a procedural map, which the game generates.
Wipe data
When does KTest wipe, and how often?
A rhythm cannot be read from the wipes of KTest 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 4 days 10 hours ago, and that is the one in play.
What is wipe day on KTest like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 1 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Lists and tags
Which Rust Data filters and lists contain KTest?
The Rust Data lists that KTest fits are: 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.
How should you read the server tags on KTest?
The game's server browser reads these tags from KTest: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
Join steps
What is the way to join KTest?
Enter client.connect 93.217.225.233:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.