KTest
Offline 93.217.227.41:28015 checked 31d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 179/500
- 124/100
- 193/225
- 144/700
- 21/200
- 45/1000
Quick answers
from the figures on this pageWipe schedule
What wipe timing does KTest follow?
To tell the rhythm of KTest, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 31 days 21 hours ago.
Lists and filters
How should you read the tags on KTest?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from KTest. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show KTest?
On Rust Metrics, KTest sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
What position does KTest hold among Rust servers?
Ranking for KTest: #14,309 on seven-day player hours, top 61% of all ranked servers.
What player count does KTest carry?
Reading for KTest: offline at this moment; last seen 31 days 17 hours ago.
Operator and location
Where does KTest sit?
Reading: location. KTest gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 93.217.227.41:28015.
What Rust version is KTest on?
Rust network protocol 2633 and build 165217 on Windows is the build KTest runs. To get in, your game needs the same protocol; Steam applies the update.
Is KTest up, and how often does it stay up?
Reading: offline. KTest last answered 31 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 26 September 2026.
Rules and settings
How is KTest configured, and what rules are in force?
No gather rate appears in the name: KTest. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.
Which map is live on KTest?
The game generates a procedural map for KTest.
Join
How do you connect to KTest?
Press F1 in Rust and enter client.connect 93.217.227.41:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.