Station XX-7029 · no signal
KTest
Offline 93.217.225.233:28015 checked 3d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #7,029
- top 32%
- Last wipe
- 4d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 slots
- Motion · 24 h
- M –not enough readings
Players
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 32% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 3.2 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 24 Oct, 13:56 UTC4d ago | M0.0■steady | 1 | – | running | 1 | |
| Wed 21 Oct, 10:09 UTC7d ago | M0.0▲rising | 1 | held half | 3.2 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on KTest?
A procedural map runs on KTest, generated by the game.
Which settings and rules apply on KTest?
The name of KTest gives no gather rate. At the game's default, groups can have up to 8 players. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on KTest right now?
A reading taken now finds KTest offline; the most recent activity was 3 days 3 hours ago. The seven-day average is 1 players, with a peak of 1.
How does KTest rank against other Rust servers?
The last seven days of player hours place KTest at #7,029, in the top 32% of all ranked servers.
Operator and location
How reliably does KTest stay online?
KTest is down at the moment; the last recorded contact was 3 days 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 26, or 15% of the time. On 18 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is KTest hosted?
A region is not published by KTest. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 93.217.225.233:28015.
What build of Rust does KTest use?
KTest is running Rust network protocol 2635 and build 168909 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on KTest?
1 players, on average, was the busiest crowd at its recent wipes. 1 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
How often does KTest wipe, and on which days?
On record so far are too few of KTest's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 4 days 5 hours is how long the current world has been running.
Lists and tags
What do the server tags on KTest mean?
Tags published by KTest and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does KTest appear?
The Rust Server Trends lists that take in KTest are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How to join
How do you connect to KTest?
To join, enter client.connect 93.217.225.233:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.