Rust Data

rustdata.spaceservers37.11.80.79:28016.ipynb

Run all rust-data · live

‹ All servers

Online 37.11.80.79:28015 checked 10m ago

Solo Server 3

teams off moddedoxide

Connect

srv = rust.server("37.11.80.79:28016")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75107:0016:0017:0002:0003:0004: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 25% 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 gap2.1 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 22 OctTue 20 OctSun 18 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, 1 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 22 Oct, 14:59 UTC6d ago 1 NaN running 1
1 Tue 20 Oct, 06:21 UTC8d ago 1 held half 2.4 days 1
2 Sun 18 Oct, 09:53 UTC10d ago 1 NaN 1.9 days 0
3 Sat 17 Oct, 09:28 UTC11d ago 1 NaN 1 days 1
4 Mon 12 Oct, 13:14 UTC16d ago 1 held half 4.8 days 1
5 Mon 5 Oct, 12:55 UTC23d ago 1 held half 7 days 1
6 Mon 5 Oct, 06:45 UTC23d ago 1 NaN 0.3 days 1
7 Fri 2 Oct, 06:33 UTC26d ago 1 held half 3 days 1
8 Thu 1 Oct, 02:48 UTC28d ago 1 NaN 1.2 days 1
9 Mon 28 Sep, 23:22 UTC30d ago 1 held half 2.1 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

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
37.11.80.79:28015
region
–
max players
10
group limit
teams off
wipe schedule
–
last wipe
22 Oct 2026, 20:01 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 average48/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 · 117 on average67/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average16/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average6/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Solo Server 3 rank?

Rank #5,649 on seven-day player hours for Solo Server 3, within the top 25% of all ranked servers.

What population does Solo Server 3 carry?

Current row: 1 players on Solo Server 3, against 10 slots. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 07:00 UTC is the busiest, at 1 players.

Server facts

What is the Rust version on Solo Server 3?

Version Rust network protocol 2635 and build 168909 on Windows is reported by Solo Server 3. The protocol has to match before you can join, and Steam does the updating.

Is Solo Server 3 up, and what does its uptime show?

Solo Server 3 reports itself online at the current refresh. 33 of 168 hours up over the last 7 full days, or 20%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Solo Server 3 sit?

For Solo Server 3, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 37.11.80.79:28015 is its address.

Map and rules

Which rules apply on Solo Server 3, and what settings?

You will not find a gather rate in the string Solo Server 3. Group limits do not appear in its data. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Wipe schedule

When does Solo Server 3 wipe, and on what schedule?

No next wipe can be predicted for Solo Server 3, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 6 days 9 hours ago.

On Solo Server 3, what happens on wipe day?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 1 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.

Lists and tags

Which lists on Rust Data hold Solo Server 3, and which filters?

These Rust Data lists include Solo Server 3: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last week.

How should you read the server tags on Solo Server 3?

These tags are published by Solo Server 3 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts0 (Group limit): No teams: the setting is disabled; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way into Solo Server 3?

The manual route: launch Rust, F1, then client.connect 37.11.80.79: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,cs168909,ts0,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts0
Group limit No teams: the setting is disabled.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 32,585 players 11,628 servers online