Rust Data

rustdata.spaceservers74.130.231.139:28027.ipynb

Run all rust-data · live

‹ All servers

Offline 74.130.231.139:28025 checked 13h ago

KSK-Labs Testing

moddedcarbon

Connect

srv = rust.server("74.130.231.139:28027")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak 1
rank #10,178 # top 46%
last wipe 5d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75120:0001:0005:0010:0014:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020020:0001:0005:0010:0014:0020: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 9 Oct. 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
15k10k15k20k9 Oct13 Oct16 Oct20 Oct25 Oct29 Oct

Top 46% 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 gap2.8 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 24 OctTue 13 OctMon 12 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 Sat 24 Oct, 00:36 UTC5d ago 1 NaN running 0
1 Tue 13 Oct, 08:22 UTC16d ago 1 NaN 10.7 days 0
2 Mon 12 Oct, 01:49 UTC17d ago 1 NaN 1.3 days 0
3 Fri 9 Oct, 07:02 UTC20d ago 1 NaN 2.8 days 1

# 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 10
No map picture published
map
Procedural Map
size
3500
seed
10
Open on RustMaps

Server

srv.info()
address
74.130.231.139:28025
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
24 Oct 2026, 00:36 UTC
hostname
–
first seen
9 Oct 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 · 149 on average143/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average135/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average189/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average78/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average10/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average19/1000

Quick answers

From the figures on this page.

Player counts

How does KSK-Labs Testing compare in the rankings?

Rank #10,178 on seven-day player hours for KSK-Labs Testing, within the top 46% of all ranked servers.

How many players does KSK-Labs Testing hold at once?

Offline now for KSK-Labs Testing, with the last sample 13 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 21:00 UTC is the busiest, at 1 players.

Server facts

What does performance look like on KSK-Labs Testing?

Server fps over the last 48 hours averages 146; the floor is 120. Entity numbers reached 71,215, and that includes buildings, deployables and the rest. The memory field tops out at 2,483 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does KSK-Labs Testing run?

Rust network protocol 2635 and build 168909 on Windows is what KSK-Labs Testing runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is KSK-Labs Testing, and is it online now?

The latest sample has KSK-Labs Testing offline, with a last sighting 13 hours ago. A restart about 23 hours ago is what its reported uptime implies. 57 of 168 hours up over the last 7 full days, or 34%. Rust Data logged it first on 9 October 2026.

Where does KSK-Labs Testing sit?

No region is published by KSK-Labs Testing. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 74.130.231.139:28025 is its address.

Rules, settings, map

What rules and settings are recorded for KSK-Labs Testing?

The name KSK-Labs Testing carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.

What is the map on KSK-Labs Testing?

Size 3,500, seed 10: the procedural map on KSK-Labs Testing, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does KSK-Labs Testing wipe, and how often?

No next wipe can be predicted for KSK-Labs Testing, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 5 days 9 hours ago.

On KSK-Labs Testing, what happens on wipe day?

Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.

Lists and tags

Where does KSK-Labs Testing appear among Rust Data lists and filters?

These Rust Data lists include KSK-Labs Testing: 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 week.

How should you read the server tags on KSK-Labs Testing?

These tags are published by KSK-Labs Testing and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 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): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way to join KSK-Labs Testing?

The manual route: launch Rust, F1, then client.connect 74.130.231.139:28025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players 100 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 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 Plugin framework: Carbon.

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,753 players 11,714 servers online