KlimoServer
Online 93.99.7.63:28115 checked 11m ago
Server instruments
last reading Tue 19:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 30 · below 20 is lag, below 10 is badEntities
48 h range 114,633–117,196 · memory 5,299 MBUptime
12 days 10 hours since its last restart, at the last readingPlayers
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, measured since 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 08:42 UTC12d ago | 0 | – | running | 0 |
| Fri 2 Oct, 15:38 UTC25d ago | 2 | halved by day 3 | 12.7 days | 0 |
| Tue 29 Sep, 05:24 UTC28d ago | 1 | held half | 3.4 days | 0 |
| Mon 28 Sep, 21:38 UTC28d ago | 1 | – | 0.3 days | 0 |
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- 244/2000
- 314/2000
- 129/200
- 19/200
- 53/250
- 56/100
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on KlimoServer?
The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 50% of recent wipes. By day 3 it fell below half when it didn't.
What wipe timing does KlimoServer follow?
There is no next wipe to predict: KlimoServer wipes at irregular times. 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 12 days 12 hours ago.
Lists and filters
How should you read the tags on KlimoServer?
These are the tags KlimoServer publishes, and the server browser reads them: 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; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does KlimoServer appear in Rust Metrics lists and filters?
These Rust Metrics lists carry KlimoServer: Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Population
What position does KlimoServer hold among Rust servers?
Ranking for KlimoServer: #15,400 on seven-day player hours, top 69% of all ranked servers.
What is the population on KlimoServer?
0 of 10 slots are filled on KlimoServer right now. A seven-day average of 0 players is the reading.
Operator and location
What location is KlimoServer hosted in?
No region comes from KlimoServer. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 93.99.7.63:28115.
What Rust version is KlimoServer on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by KlimoServer. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for KlimoServer?
Over the last 48 hours the average was 30 server fps; the floor was 30. Reading: 117,196 entities at the highest. That covers buildings, deployables and everything else. Reading: 5,922 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
Is KlimoServer up, and how often does it stay up?
KlimoServer reports online. Status: normal. Reading: uptime. About 12 days 10 hours ago it restarted, on its own count. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 28 September 2026, recorded by Rust Metrics.
Settings and map
What rules does KlimoServer enforce, and what are its settings?
Reading the name gives no gather rate for KlimoServer. The group cap is 8 players, which is the default in the game. Mode check gives pve; no combat against other players. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on KlimoServer?
Size 4,500 and seed 2113013598: the game generates the procedural map on KlimoServer from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Connection
What do you do to join KlimoServer?
Press F1 in Rust and enter client.connect 93.99.7.63:28115. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.