@kuuzin
Offline 89.124.67.88:28015 checked 7d ago
Server instruments
no direct query in 48 hoursPlayers now
7% full 7-day avg7-day peakServer 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 63% 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- 650/700
- 45/250
- 87/250
- 365/400
- 165/200
- 157/225
Quick answers
from the figures on this pageWipe timing
What wipe timing does @kuuzin follow?
To tell the rhythm of @kuuzin, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 16 days 4 hours ago.
Lists and filters
Which tags does @kuuzin carry, and what do they mean?
These are the tags @kuuzin publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): Slots: 15; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show @kuuzin?
Rust Metrics lists featuring @kuuzin: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does @kuuzin sit in the rankings?
Ranking for @kuuzin: #13,862 on seven-day player hours, top 63% of all ranked servers.
What player count does @kuuzin carry?
@kuuzin is not responding; status offline, last seen 7 days 6 hours ago. Seven-day check: 1 players on average. Peak reading: 1.
Operator and location
Which location does @kuuzin run from?
No region comes from @kuuzin. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 89.124.67.88:28015.
What Rust version is @kuuzin on?
Reading: @kuuzin, Rust network protocol 2634 and build 167781, Windows. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is @kuuzin, and is it online now?
Reading: offline. @kuuzin last answered 7 days 6 hours ago. Uptime for the last 6 full days: 0 of 144 hours, or 0%. Check: first contact. Rust Metrics logged it on 20 October 2026.
Settings and map
What rules does @kuuzin enforce, and what are its settings?
Reading the name gives no gather rate for @kuuzin. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on @kuuzin?
The game generates a procedural map for @kuuzin.
Connection
How can you get onto @kuuzin?
To join: start Rust, press F1 and type client.connect 89.124.67.88:28015. Or press Launch Rust here and Steam opens the game and connects you.