Kirusha's Private Test
Offline 95.72.7.133:28015 checked 24d ago
Measurements
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
Top 70% 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
| 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.
Quick answers
Population
How does Kirusha's Private Test rank against other Rust servers?
Over the past week it ranks #15,958 for player hours, which puts Kirusha's Private Test in the top 70% of all ranked servers.
How busy is Kirusha's Private Test?
Kirusha's Private Test is offline at this count; we last saw it 24 days 19 hours ago.
Lists and tags
What do the server tags on Kirusha's Private Test mean?
The game's server browser reads the tags Kirusha's Private Test publishes: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The server has 10 slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): To join, your game must match protocol 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include Kirusha's Private Test?
Kirusha's Private Test appears among the Rust Population lists that follow: Community servers, field-listed. Filter the server list by Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more and it will show up.
Wipe schedule
What is the wipe schedule on Kirusha's Private Test?
Its rhythm cannot be told yet: too few of Kirusha's Private Test's wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. Counted from 24 days 20 hours ago, that is how long the current world has stood.
Settings
Which map does Kirusha's Private Test run?
The map on Kirusha's Private Test is procedural, made by the game.
What are the rules and settings on Kirusha's Private Test?
Nothing in Kirusha's Private Test's name says how gather works. The group limit is 8 players, which is the default. This server runs survival, raid, build and gather: the standard game. Combat between players, raids included, is permitted. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, runs here.
About the server
Which version of Rust does Kirusha's Private Test run?
Rust network protocol 2634 and build 166652 on Windows is what Kirusha's Private Test uses. Your game needs the same protocol to join; Steam takes care of updating it.
Is Kirusha's Private Test online, and how reliable is it?
Offline at the moment, Kirusha's Private Test was last seen 24 days 19 hours ago. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. It was first seen by Rust Population on 3 October 2026.
Where is Kirusha's Private Test located?
Nothing published by Kirusha's Private Test states a region. Rust Population does not look up where the machine stands; it shows where the server says it is. 95.72.7.133:28015 is where it lives.
Getting in
How do I join Kirusha's Private Test?
To connect directly, open Rust's console with F1 and type client.connect 95.72.7.133:28015; or press Launch Rust on this page and Steam opens Rust and joins for you.