KTest
Offline 93.227.102.165:28015 checked 39d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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 bestWipe 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- 167/500
- 124/100
- 182/225
- 70/700
- 13/200
- 20/1000
Quick answers
from the figures on this pageWipe timing
When does KTest wipe?
The rhythm of KTest's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 54 days 4 hours ago the current world was made.
Tag meanings
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): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server 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?
Rust Metrics lists featuring KTest: 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
Where does KTest sit in the rankings?
Ranking for KTest: #14,101 on seven-day player hours, top – of all ranked servers.
What is the population on KTest?
Status for KTest: offline. Last seen 39 days 22 hours ago.
Server
What location is KTest hosted in?
Reading: location. KTest gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 93.227.102.165:28015.
What Rust version is KTest on?
Reading: KTest, Rust network protocol 2633 and build 164530, Windows. 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 39 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What rules does KTest enforce, and what are its settings?
Check: gather rate. The name KTest does not state one. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is KTest on?
Procedural map on KTest, made by the game's generator.
Connection
How can you get onto KTest?
To join: start Rust, press F1 and type client.connect 93.227.102.165:28015. Or press Launch Rust here and Steam opens the game and connects you.