Rust Data

rustdata.spaceservers80.242.59.137:35502.ipynb

Run all rust-data · live

‹ All servers

Offline 80.242.59.137:35510 checked 34d ago

sran' inc. | STAGING (aux01)

moddedcarbon

Connect

srv = rust.server("80.242.59.137:35502")
print(srv.connect_command)

Right now

srv.summary()
players now 0/1000 # 0% full
7-day average 0 # peak –
rank #16,363 # top 71%
last wipe 34d ago # no schedule published
next wipe – # no rhythm it keeps
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
No hourly history yet.

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, 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 Sep22 Sep25 Sep27 Sep30 Sep2 Oct

Top 71% 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 gap0.3 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Fri 25 SepThu 24 SepThu 24 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 Fri 25 Sep, 05:24 UTC34d ago 0 NaN running 0
1 Thu 24 Sep, 18:03 UTC35d ago 0 NaN 0.5 days 0
2 Thu 24 Sep, 11:32 UTC35d ago 0 NaN 0.3 days 0
3 Thu 24 Sep, 04:29 UTC35d ago 0 NaN 0.3 days 0
4 Wed 23 Sep, 22:15 UTC36d ago 0 NaN 0.3 days 0
5 Wed 23 Sep, 15:28 UTC36d ago 2 NaN 0.3 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 789552
Custom map, no picture published
map
SRAN MAP
size
4500
seed
789552

Server

srv.info()
address
80.242.59.137:35510
region
–
max players
1000
group limit
8, the default
wipe schedule
–
last wipe
25 Sep 2026, 05:24 UTC
hostname
–
first seen
16 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 average20/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average125/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 122 on average47/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average8/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average31/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average52/200

Quick answers

From the figures on this page.

Population data

How does sran' inc. | STAGING (aux01) compare in the rankings?

Player hours over seven days put sran' inc. | STAGING (aux01) at #16,363, in the top 71% of the ranked set.

What population does sran' inc. | STAGING (aux01) carry?

Offline now for sran' inc. | STAGING (aux01), with the last sample 34 days 13 hours ago.

Server facts

Which Rust version is sran' inc. | STAGING (aux01) on?

The build is Rust network protocol 2633 and build 165585 on Windows, run by sran' inc. | STAGING (aux01). Steam updates your game for you, but the protocol must match to join.

Is sran' inc. | STAGING (aux01) up, and what does its uptime show?

sran' inc. | STAGING (aux01) is offline at this refresh; the last response came 34 days 13 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 16 September 2026.

Where does sran' inc. | STAGING (aux01) sit?

No region is published by sran' inc. | STAGING (aux01). The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 80.242.59.137:35510.

Rules, settings, map

Which settings and rules does sran' inc. | STAGING (aux01) run?

The name sran' inc. | STAGING (aux01) carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has sran' inc. | STAGING (aux01) loaded?

The game generates the map on sran' inc. | STAGING (aux01): procedural, size 4,500, seed 789552. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: SRAN MAP.

Wipe schedule

On what schedule does sran' inc. | STAGING (aux01) wipe?

No next wipe can be predicted for sran' inc. | STAGING (aux01), which wipes at irregular times. 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 34 days 23 hours ago, and that is the one in play.

On sran' inc. | STAGING (aux01), what happens on wipe day?

Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Where does sran' inc. | STAGING (aux01) appear among Rust Data lists and filters?

On Rust Data, sran' inc. | STAGING (aux01) appears in these lists: 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.

How should you read the server tags on sran' inc. | STAGING (aux01)?

These tags are published by sran' inc. | STAGING (aux01) and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1000 (Max players): 1,000 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165585 (Build): Build number: 165585; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into sran' inc. | STAGING (aux01)?

Enter client.connect 80.242.59.137:35510 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://discord.com/invite/sran.

Server tags · what each one means

srv.tags.decode()

Published as mp1000,ptrak,$r?,v2633,gmrust,cs165585,ts8,^z,^y

Game

gmrust
Game mode Rust survival in its standard form.
mp1000
Max players 1,000 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol Protocol 2633 is required; a different game version cannot connect.
cs165585
Build Build number: 165585.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon The plugin framework in use is 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 40,937 players 11,633 servers online