Rust Data

rustdata.spaceservers199.60.101.90:28037.ipynb

Run all rust-data · live

‹ All servers

Online 199.60.101.90:28035 checked 9m ago

Kai

moddedcarbon

Connect

srv = rust.server("199.60.101.90:28037")
print(srv.connect_command)

Right now

srv.summary()
players now 0/30 # 0% full
7-day average 0 # peak 1
rank #8,085 # top 36%
last wipe 2d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75100:0009:0018:0002:0011:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510000:0009:0018:0002:0011:0021: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 17 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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 36% 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 gap9.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 4.5

The first 48 hours of its last wipes

Mon 26 OctSat 10 OctThu 8 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 26 Oct, 07:13 UTC2d ago 1 NaN running 0
1 Sat 10 Oct, 05:00 UTC18d ago 1 halved by day 8 16.1 days 0
2 Thu 8 Oct, 02:48 UTC20d ago 1 halved by day 1 2.1 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

3500 · seed 1215
Map of Kai
map
Procedural Map
size
3500
seed
1215
Open on RustMaps

Server

srv.info()
address
199.60.101.90:28035
region
–
max players
30
group limit
8, the default
wipe schedule
–
last wipe
26 Oct 2026, 08:04 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 157 on average61/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average134/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average61/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average51/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average16/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average9/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Kai rank?

Over the last seven days Kai sits at #8,085 on player hours, in the top 36% of ranked servers.

How full does Kai run?

Kai reports 0 players at this refresh, with 30 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 00:00 UTC, mean 1 players.

Server data

How well does Kai perform?

Server fps over the last 48 hours averages 79; the floor is 60. Buildings, deployables and all else in the world took the count as high as 70,193 entities. The memory field tops out at 2,606 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does Kai run?

Version Rust network protocol 2635 and build 168909 on Windows is reported by Kai. The protocol has to match before you can join, and Steam does the updating.

Is Kai up, and what does its uptime show?

The current sample puts Kai online. The uptime it reports puts the last restart about 2 days 12 hours ago. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Kai sit?

For Kai, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 199.60.101.90:28035 is its address.

Map and rules

What rules and settings are recorded for Kai?

No gather rate appears in the name: Kai. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.

What is the map on Kai?

The game generates the map on Kai: procedural, size 3,500, seed 1215. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

On what schedule does Kai wipe?

Kai 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. A new world was started 2 days 14 hours ago, and that is the one in play.

On Kai, what happens on wipe day?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 4.5 in the other cases.

Tags, lists

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

These Rust Data lists include Kai: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

Which meanings do the tags on Kai hold?

The game's server browser reads these tags from Kai: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): The server lists 30 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. 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 Kai?

In Rust, F1 opens the console: type client.connect 199.60.101.90:28035. 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 mp30,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Rust survival in its standard form.
mp30
Max players The server lists 30 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^z
Modded Plugins or settings alter the game, so it sits under Modded.
^y
Carbon Runs on Carbon for plugins.

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 56,681 players 11,752 servers online