RUST METRICSFlight deck · live data
Data live Servers11,739 Players61,775 Populated3,380 Fresh wipes 3 h186 Scan5 min
‹ All servers203.16.163.36:20797
Online Full Queue Fresh wipe Wipe due No query

RUBIN.EXE

Online 203.16.163.36:20797 checked 11m ago

moddedcarbon
COM 1 · connect

Server instruments

last reading Thu 10:00 UTC
0 8 15 22 30 PAX 0 /30

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 217 SERVER FPS

Server fps

48 h low 198 · below 20 is lag, below 10 is bad
0 10 20 30 40 ENT 28,066 ×1000

Entities

48 h range 27,866–30,383 · memory 3,151 MB
1239 ET SINCE RESTART 2D 23H

Uptime

2 days 23 hours since its last restart, at the last reading
7-day average0peak 4
Rank#5,546top 25%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
Memory3,151MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5212:0021:0006:0015:0001:0010:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040012:0021:0006:0015:0001:0010: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.

REC 3

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.

PLAN

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 gap8.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 22:05 UTC FW27d ago 3 – running 0
Tue 15 Sep, 10:01 UTC44d ago 1 halved by day 5 16.5 days 0
Mon 14 Sep, 01:21 UTC45d ago 1 – 1.4 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on RUBIN.EXE when wipe day comes?

The busiest point of its recent wipes drew 2 players on average. 18 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 5 it fell below half.

When does RUBIN.EXE wipe?

No next wipe can be predicted for RUBIN.EXE, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 27 days 13 hours ago.

Tags

How should you read the tags on RUBIN.EXE?

These are the tags RUBIN.EXE publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp30 (Max players): Slots: 30; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Check: framework. Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does RUBIN.EXE appear in Rust Metrics lists and filters?

Rust Metrics lists featuring RUBIN.EXE: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

What position does RUBIN.EXE hold among Rust servers?

Ranking for RUBIN.EXE: #5,546 on seven-day player hours, top 25% of all ranked servers.

What is the population on RUBIN.EXE?

Current headcount on RUBIN.EXE: 0 players, 30 slots available. Check: players over seven days. Average 0, peak 4. Check: 48-hour peak. 20:00 UTC, 1 players on average.

Server

What location is RUBIN.EXE hosted in?

Reading: location. RUBIN.EXE gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 203.16.163.36:20797.

What Rust version is RUBIN.EXE on?

Reading: RUBIN.EXE, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for RUBIN.EXE?

Over the last 48 hours the average was 226 server fps; the floor was 198. Peak entity count: 30,383. Buildings, deployables and all else included. Reading: 3,712 MB of memory at the highest. Expect lag when fps falls and entities climb.

How reliable is RUBIN.EXE, and is it online now?

Check: connection. RUBIN.EXE is online at this moment. By its reported uptime, the last restart was roughly 2 days 23 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

How is RUBIN.EXE configured, and what rules are in force?

Reading the name gives no gather rate for RUBIN.EXE. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. VAC is off. That is Valve's anti-cheat.

What map is RUBIN.EXE on?

From seed 50000, the game generates the procedural map on RUBIN.EXE. Its size is 2,500. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join RUBIN.EXE?

To join: start Rust, press F1 and type client.connect 203.16.163.36:20797. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp30
Max players Slots: 30.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Check: framework. 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.