Rust Data

rustdata.spaceservers93.99.7.63:28116.ipynb

Run all rust-data · live

‹ All servers

Offline 93.99.7.63:28115 checked 5h ago

KlimoServer

moddedoxidepve

Connect

srv = rust.server("93.99.7.63:28116")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,423 # top 69%
last wipe 12d ago # no schedule published
next wipe – # no rhythm it keeps
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123406:0014:0023:0007:0016:0000:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304006:0014:0023:0007:0016:0000:00

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 best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k28 Sep4 Oct10 Oct16 Oct22 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap3.4 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 3

The first 48 hours of its last wipes

Thu 15 OctFri 2 OctTue 29 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 15 Oct, 08:42 UTC12d ago 0 NaN running 0
1 Fri 2 Oct, 15:38 UTC25d ago 2 halved by day 3 12.7 days 0
2 Tue 29 Sep, 05:24 UTC29d ago 1 held half 3.4 days 0
3 Mon 28 Sep, 21:38 UTC29d ago 1 NaN 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.

display(srv.map, srv.info())

Map

4500 · seed 2113013598
Map of KlimoServer
map
Procedural Map
size
4500
seed
2113013598
Open on RustMaps

Server

srv.info()
address
93.99.7.63:28115
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
15 Oct 2026, 08:42 UTC
hostname
–
first seen
28 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 245 on average188/2000
1[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 235 on average83/2000
2Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 99 on average87/200
3【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 59 on average57/200
4TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 53 on average17/100
5Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsidgroups of 8+ · biweekly · 52 on average21/250

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does KlimoServer rank?

Player hours over seven days put KlimoServer at #15,423, in the top 69% of the ranked set.

How many players does KlimoServer hold at once?

Offline now for KlimoServer, with the last sample 5 hours ago. Over the last seven days it averaged 0 players.

Server data

What does performance look like on KlimoServer?

Server fps over the last 48 hours averages 30; the floor is 30. The entity count peaked at 117,196, covering buildings, deployables and the rest of the world. The memory field tops out at 5,922 MB. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on KlimoServer?

The build is Rust network protocol 2634 and build 167781 on Windows, run by KlimoServer. The protocol has to match before you can join, and Steam does the updating.

How reliable is KlimoServer, and is it online now?

Offline now for KlimoServer, last seen 5 hours ago. Count back 12 days 14 hours from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 28 September 2026.

Which location does KlimoServer run from?

No region is published by KlimoServer. Rust Data does not look up where the machine stands; it shows where a server says it is. 93.99.7.63:28115 is its address.

Map and rules

Which rules apply on KlimoServer, and what settings?

The name KlimoServer carries no gather rate. The group limit sits at the default of 8 players. Recorded as pve, no combat between players. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

What is the map on KlimoServer?

Size 4,500, seed 2113013598: the procedural map on KlimoServer, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

On what schedule does KlimoServer wipe?

KlimoServer wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 12 days 20 hours ago.

On KlimoServer, what happens on wipe day?

Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 50% of the time. In the wipes where it did not hold, half was lost by day 3.

Tags, lists

Which lists on Rust Data hold KlimoServer, and which filters?

On Rust Data, KlimoServer appears in these lists: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: 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.

How should you read the server tags on KlimoServer?

The game's server browser reads these tags from KlimoServer: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to KlimoServer?

In Rust, F1 opens the console: type client.connect 93.99.7.63:28115. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2634,^p,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players The server lists 10 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol To join, your game must run protocol 2634.
cs167781
Build Build number: 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 33,161 players 11,582 servers online