Rust Data

rustdata.spaceservers146.66.202.157:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 146.66.202.157:28015 checked 9h ago

Rust Lab | Carbon

moddedcarbon

Connect

srv = rust.server("146.66.202.157:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/20 # 0% full
7-day average 1 # peak 2
rank #9,270 # top 42%
last wipe 10h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.511.5212:0013:0015:0016:0018:0019:00Wiped Thu 29 Oct, 17:24 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
010020030040012:0013:0015:0016:0018:0019:00Wiped Thu 29 Oct, 17:24 UTCWIPE

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 29 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
15k10k15k20k20 Sep7 Oct11 Oct14 Oct18 Oct30 Oct

Top 42% 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 gap11 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Wed 7 OctWed 7 OctTue 15 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 29 Oct, 17:24 UTC10h ago NaN NaN running 1
1 Thu 29 Oct, 11:16 UTC17h ago NaN NaN NaN 1
2 Wed 7 Oct, 19:25 UTC22d ago NaN NaN 21.7 days 1
3 Wed 7 Oct, 07:44 UTC22d ago 1 NaN 0.5 days 1
4 Tue 15 Sep, 19:09 UTC44d ago 1 NaN 21.5 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

4500 · seed 2138400164
Map of Rust Lab | Carbon
map
Procedural Map
size
4500
seed
2138400164
Open on RustMaps

Server

srv.info()
address
146.66.202.157:28015
region
–
max players
20
group limit
8, the default
wipe schedule
–
last wipe
29 Oct 2026, 17:24 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 · 151 on average19/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average126/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 122 on average51/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average9/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average29/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average49/200

Quick answers

From the figures on this page.

Player counts

What position does Rust Lab | Carbon take in the server rankings?

Rank #9,270 on seven-day player hours for Rust Lab | Carbon, within the top 42% of all ranked servers.

What population does Rust Lab | Carbon carry?

Rust Lab | Carbon returns no live count at this refresh, having last been seen 9 hours ago. Over the last seven days it averaged 1 players and peaked at 2. The 48-hour sample puts the busiest hour at 16:00 UTC, averaging 2 players.

Server facts

How well does Rust Lab | Carbon perform?

Server fps over the last 48 hours averages 170; the floor is 138. The entity count peaked at 115,226, covering buildings, deployables and the rest of the world. A high of 3,170 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is Rust Lab | Carbon on?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Rust Lab | Carbon. Steam updates your game for you, but the protocol must match to join.

Is Rust Lab | Carbon up, and what does its uptime show?

The latest sample has Rust Lab | Carbon offline, with a last sighting 9 hours ago. The uptime it reports puts the last restart about 44 minutes ago. Over the last 7 full days the hours up number 8 of 168, 5%. Rust Data logged it first on 13 September 2026.

Which location does Rust Lab | Carbon run from?

For Rust Lab | Carbon, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 146.66.202.157:28015.

Rules, settings, map

Which rules apply on Rust Lab | Carbon, and what settings?

The name Rust Lab | Carbon carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. Anti-cheat status: VAC on.

Which map has Rust Lab | Carbon selected?

Size 4,500, seed 2138400164: the procedural map on Rust Lab | Carbon, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

On what schedule does Rust Lab | Carbon wipe?

Rust Lab | Carbon 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 10 hours ago, and that is the one in play.

On Rust Lab | Carbon, what happens on wipe day?

The average peak over recent wipes is 1 players.

Lists and tags

Which lists on Rust Data hold Rust Lab | Carbon, and which filters?

On Rust Data, Rust Lab | Carbon appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.

Which meanings do the tags on Rust Lab | Carbon hold?

Read by the game's server browser, the tags Rust Lab | Carbon publishes are: gmrust (Game mode): Survival play, standard Rust; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way to join Rust Lab | Carbon?

Enter client.connect 146.66.202.157:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp20
Max players The server lists 20 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

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 41,075 players 11,634 servers online