Rust Data

rustdata.spaceservers80.242.59.137:35503.ipynb

Run all rust-data · live

‹ All servers

Offline 80.242.59.137:35530 checked 34d ago

sran' inc. | STAGING (aux03)

moddedcarbon

Connect

srv = rust.server("80.242.59.137:35503")
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.6 daysbetween real wipes
on rhythm67%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:29 UTC34d ago 0 NaN running 0
1 Thu 24 Sep, 13:34 UTC35d ago 0 NaN 0.7 days 0
2 Thu 24 Sep, 05:29 UTC35d ago 0 NaN 0.3 days 0
3 Wed 23 Sep, 15:28 UTC36d ago 0 NaN 0.6 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:35530
region
–
max players
1000
group limit
8, the default
wipe schedule
–
last wipe
25 Sep 2026, 05:29 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 average20/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average123/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 122 on average39/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average5/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average23/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average96/200

Quick answers

From the figures on this page.

Population

What position does sran' inc. | STAGING (aux03) take in the server rankings?

Rank #16,363 on seven-day player hours for sran' inc. | STAGING (aux03), within the top 71% of all ranked servers.

How full does sran' inc. | STAGING (aux03) run?

The current row shows sran' inc. | STAGING (aux03) offline; the last response was 34 days 13 hours ago.

Server facts

What is the Rust version on sran' inc. | STAGING (aux03)?

The build is Rust network protocol 2632 and build 159594 on Windows, run by sran' inc. | STAGING (aux03). The protocol has to match before you can join, and Steam does the updating.

How reliable is sran' inc. | STAGING (aux03), and is it up?

The latest sample has sran' inc. | STAGING (aux03) offline, with a last sighting 34 days 13 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Which location does sran' inc. | STAGING (aux03) run from?

For sran' inc. | STAGING (aux03), 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 80.242.59.137:35530.

Settings and map

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

The name sran' inc. | STAGING (aux03) 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. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.

What is the map on sran' inc. | STAGING (aux03)?

sran' inc. | STAGING (aux03) runs a procedural map of size 4,500 with seed 789552, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. SRAN MAP is what the map name field says.

Wipes and dates

When does sran' inc. | STAGING (aux03) wipe, and how often?

Irregular wipe times on sran' inc. | STAGING (aux03) leave no next wipe to forecast. 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 34 days 22 hours ago, and that is the one in play.

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

Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.

Tags, lists

Which Rust Data filters and lists contain sran' inc. | STAGING (aux03)?

The Rust Data lists that sran' inc. | STAGING (aux03) fits are: Modded Rust servers. These filters bring it up on the server list: 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 (aux03)?

The game's server browser reads these tags from sran' inc. | STAGING (aux03): gmrust (Game mode): Survival play, standard Rust; mp1000 (Max players): Slot count: 1,000; ts8 (Group limit): Team limit of 8, as shipped by default; v2632 (Protocol): The server speaks protocol 2632, so match your game version; cs159594 (Build): Build number: 159594; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. 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 sran' inc. | STAGING (aux03)?

The manual route: launch Rust, F1, then client.connect 80.242.59.137:35530. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. 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?,v2632,gmrust,cs159594,ts8,^z,^y

Game

gmrust
Game mode Survival play, standard Rust.
mp1000
Max players Slot count: 1,000.
ts8
Group limit Team limit of 8, as shipped by default.
v2632
Protocol The server speaks protocol 2632, so match your game version.
cs159594
Build Build number: 159594.
ptrak
Networking The network layer is RakNet, standard for the game.
$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 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 43,200 players 11,655 servers online