Rust Data

rustdata.spaceservers107.211.211.138:29016.ipynb

Run all rust-data · live

‹ All servers

Online 107.211.211.138:29015 checked 10m ago

[US] Chrispy Staging

Connect

srv = rust.server("107.211.211.138:29016")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75111:0020:0005:0013:0023:0008:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020011:0020:0005:0013:0023:0008: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 Sep6 Oct13 Oct21 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 gap11 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Wed 21 OctWed 30 SepTue 29 Sep
01234+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 Wed 21 Oct, 22:05 UTC7d ago 0 NaN running 0
1 Wed 30 Sep, 18:44 UTC28d ago 3 halved by day 1 21.1 days 0
2 Tue 29 Sep, 20:04 UTC29d ago 3 NaN 0.9 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 1337
Map of [US] Chrispy Staging
map
Procedural Map
size
4500
seed
1337
Open on RustMaps

Server

srv.info()
address
107.211.211.138:29015
region
– · us5
max players
50
group limit
8, the default
wipe schedule
–
last wipe
21 Oct 2026, 22:05 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
0Rusty Moose |US Main|NA · groups of 12+ · weekly · 251 on average18/250
1Rustoria.co - US MainNA · groups of 16+ · weekly · 236 on average19/250
2Rusty Moose |US Mondays|NA · groups of 12+ · weekly · 206 on average165/250
3Rustoria.co - US MondaysNA · groups of 12+ · weekly · 158 on average133/200
4Rustafied.com - US FridayNA · groups of 16+ · weekly · 155 on average6/100
5Rustopia.gg - US Main PremiumNA · groups of 16+ · weekly · 145 on average11/200

Quick answers

From the figures on this page.

Player counts

How does [US] Chrispy Staging compare in the rankings?

Rank #10,219 on seven-day player hours for [US] Chrispy Staging, within the top 46% of all ranked servers.

What population does [US] Chrispy Staging carry?

The sample now reads 0 players for [US] Chrispy Staging, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 11:00 UTC, mean 1 players.

Server data

How well does [US] Chrispy Staging perform?

Averaged over 48 hours: 139 server fps, never under 102. The entity count peaked at 120,000, covering buildings, deployables and the rest of the world. The memory field tops out at 2,866 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does [US] Chrispy Staging run?

The build is Rust network protocol 2635 and build 169317 on Windows, run by [US] Chrispy Staging. The protocol has to match before you can join, and Steam does the updating.

Is [US] Chrispy Staging up, and what does its uptime show?

[US] Chrispy Staging reports itself online at the current refresh. A restart about 42 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is [US] Chrispy Staging hosted?

The name of [US] Chrispy Staging points to North America, even though no region tag is published; the region code is us5. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 107.211.211.138:29015.

Settings and map

Which settings and rules does [US] Chrispy Staging run?

The name [US] Chrispy Staging carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.

Which map has [US] Chrispy Staging selected?

[US] Chrispy Staging runs a procedural map of size 4,500 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does [US] Chrispy Staging wipe, and on what schedule?

No next wipe can be predicted for [US] Chrispy Staging, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 7 days 11 hours ago.

On [US] Chrispy Staging, what happens on wipe day?

Recent wipes averaged 2 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The drop under half arrived by day 1 in the other cases.

Lists and tags

Which lists on Rust Data hold [US] Chrispy Staging, and which filters?

These Rust Data lists include [US] Chrispy Staging: Rust community servers, unfiltered and North America Rust servers. Under these filters on the server list, it is listed: Region: North America; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on [US] Chrispy Staging hold?

These tags are published by [US] Chrispy Staging and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs169317 (Build): Recorded game build: 169317; ptrak (Networking): The network layer is RakNet, standard for the game; $rus5 (Region code): us5 is the region code recorded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

How can I connect to [US] Chrispy Staging?

Enter client.connect 107.211.211.138:29015 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 mp50,ptrak,$rus5,v2635,gmrust,cs169317,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players Slot count: 50.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs169317
Build Recorded game build: 169317.
ptrak
Networking The network layer is RakNet, standard for the game.
$rus5
Region code us5 is the region code recorded.

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 53,611 players 11,695 servers online