Rust Server TrendsSeismic network · station log
Recording Stations11,695 Players53,611 Active3,212 Wipes · 3 h134 48 h

Station XX-5546 · recording

RUBIN.EXE

Online 203.16.163.36:20797 checked 11m ago

moddedcarbon
Connect
Players now
0/ 30
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 4
Rank
#5,546
top 25%
Last wipe
27d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-5546 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 30 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−1into Tue 21:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5211:0020:0005:0013:0023:0008:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040011: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 25% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
8.9 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
0%else halves by day 5

The first 48 hours of its last wipes

Thu 1 OctTue 15 SepMon 14 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 18 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 22:05 UTC FW27d ago M0.5rising 3 – running 0
Tue 15 Sep, 10:01 UTC43d ago M0.0rising 1 halved by day 5 16.5 days 0
Mon 14 Sep, 01:21 UTC45d ago M0.0rising 1 – 1.4 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 149 on average
132/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
127/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
187/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
75/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
10/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
22/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on RUBIN.EXE?

RUBIN.EXE runs a procedural map of size 2,500 with seed 50000, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on RUBIN.EXE?

No gather rate appears in the name of RUBIN.EXE. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Carbon is the plugin framework it runs. The server has VAC off, Valve's anti-cheat.

Live population

What is the current population on RUBIN.EXE?

0 of the 30 slots on RUBIN.EXE are filled right now. Across seven days this server recorded an average of 0 players and a peak of 4. The busiest point in the last 48 hours came at 20:00 UTC, averaging 1 players.

How does RUBIN.EXE rank against other Rust servers?

Over the last seven days, RUBIN.EXE recorded enough player hours to reach #5,546 worldwide, placing it in the top 25% of all ranked servers.

Operator and location

How reliably does RUBIN.EXE stay online?

As recorded now, RUBIN.EXE is running. Its reported uptime points to a restart about 2 days 21 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

How well does RUBIN.EXE perform under load?

Its average server fps over the last 48 hours was 226, and it never dropped below 198. Buildings, deployables and all the rest of the world's entities brought it to a high of 30,383. It reached a ceiling of 3,712 MB of memory. Low fps together with a growing entity count is what players experience as lag.

Where in the world is RUBIN.EXE hosted?

Nothing about a region comes from RUBIN.EXE. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 203.16.163.36:20797.

Which Rust version is RUBIN.EXE running?

Rust network protocol 2635 and build 168909 on Linux is what RUBIN.EXE runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on RUBIN.EXE?

2 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 18 hours after the wipe. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. It fell under half by day 5 in the wipes where it didn't hold.

How often does RUBIN.EXE wipe, and on which days?

There is no next wipe to predict at RUBIN.EXE, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 27 days 11 hours.

Lists and tags

What do the server tags on RUBIN.EXE mean?

The game's server browser reads the tags RUBIN.EXE publishes: gmrust (Game mode): The game mode is standard Rust survival; mp30 (Max players): 30 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does RUBIN.EXE appear?

The Rust Server Trends lists that take in RUBIN.EXE are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

How to join

What steps get you onto RUBIN.EXE?

Enter client.connect 203.16.163.36:20797 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp30,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode The game mode is standard Rust survival.
mp30
Max players 30 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon Carbon is the plugin framework running here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.