Rust Data

rustdata.spaceservers60.111.53.135:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 60.111.53.135:28015 checked 6h ago

c1tas

Connect

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

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75111:0023:0005:0010:0000:0003:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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. 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 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 gap4.8 daysbetween real wipes
on rhythm43%of its recent wipes
wipe-day peak1players, last three wipes
crowd held67%else halves by day 5

The first 48 hours of its last wipes

Mon 26 OctWed 21 OctThu 1 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, 3 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 28 Oct, 11:44 UTC22h ago NaN NaN running 0
1 Mon 26 Oct, 00:09 UTC3d ago 1 held half 2.5 days 0
2 Wed 21 Oct, 08:37 UTC8d ago 1 NaN 4.6 days 0
3 Thu 1 Oct, 19:57 UTC FW27d ago 1 held half 19.5 days 0
4 Thu 24 Sep, 19:04 UTC34d ago 1 halved by day 5 7 days 0
5 Sat 19 Sep, 22:54 UTC39d ago 1 NaN 4.8 days 0
6 Tue 15 Sep, 12:22 UTC43d ago 1 halved by day 1 4.4 days 0
7 Thu 3 Sep, 20:19 UTC FW55d ago NaN NaN 11.7 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
60.111.53.135:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
26 Oct 2026, 02:54 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 |EU Mondays|EU · groups of 12+ · weekly · 522 on average322/375
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average322/325
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average32/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average35/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average48/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 246 on average162/200

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does c1tas rank?

Rank #7,922 on seven-day player hours for c1tas, within the top 36% of all ranked servers.

How full does c1tas run?

c1tas returns no live count at this refresh, having last been seen 6 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 23:00 UTC, mean 1 players.

About the server

What Rust version does c1tas run?

Version Rust network protocol 2635 and build 169097 on Windows is reported by c1tas. Steam updates your game for you, but the protocol must match to join.

How reliable is c1tas, and is it online now?

c1tas is offline at this refresh; the last response came 6 hours ago. Over the last 7 full days the hours up number 33 of 168, 20%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does c1tas sit?

No region is published by c1tas. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 60.111.53.135:28015 is its address.

Rules, settings, map

Which settings and rules does c1tas run?

You will not find a gather rate in the string c1tas. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has c1tas loaded?

The game generates its map: procedural, on c1tas.

Wipe data

On what schedule does c1tas wipe?

c1tas wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 3 days 6 hours ago, and that is the one in play.

On c1tas, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 3 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 67% of the time. In the wipes where it did not hold, half was lost by day 5.

Lists and tags

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

The Rust Data lists that c1tas fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Which meanings do the tags on c1tas hold?

These tags are published by c1tas and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs169097 (Build): Recorded game build: 169097; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. 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.

How to join

What is the way to join c1tas?

The manual route: launch Rust, F1, then client.connect 60.111.53.135:28015. 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 mp10,ptrak,$r?,v2635,gmrust,cs169097,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs169097
Build Recorded game build: 169097.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

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 51,773 players 11,668 servers online