RUST METRICSFlight deck · live data
Data live Servers11,664 Players43,407 Populated3,022 Fresh wipes 3 h91 Scan5 min
‹ All servers95.70.185.216:28015
Offline Full Queue Fresh wipe Wipe due No query

s2

Offline 95.70.185.216:28015 checked 12h ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

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

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average1peak 1
Rank#7,648top 34%
Last wipe10d agono schedule published
Next wipe–no rhythm it keeps
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75117:0018:0013:00

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 34% 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 gap6.8 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 4

The first 48 hours of its last wipes

Sat 17 OctSun 4 OctSat 3 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 05:55 UTC10d ago 1 – running 0
Sun 4 Oct, 01:48 UTC24d ago 1 halved by day 4 13.2 days 0
Sat 3 Oct, 16:28 UTC24d ago 1 – 0.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 s2 when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 1 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 4 it fell below half when it didn't.

How often does s2 wipe, and when?

No next wipe can be predicted for s2, 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. 10 days 20 hours ago the current world was made.

Lists and filters

How should you read the tags on s2?

These are the tags s2 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does s2 appear in Rust Metrics lists and filters?

On Rust Metrics, s2 sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

What position does s2 hold among Rust servers?

Ranking for s2: #7,648 on seven-day player hours, top 34% of all ranked servers.

What is the population on s2?

s2 is not responding; status offline, last seen 12 hours ago. Seven-day check: 1 players on average. Peak reading: 1. Check: 48-hour peak. 18:00 UTC, 1 players on average.

Server

Where does s2 sit?

Reading: location. s2 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 95.70.185.216:28015.

What Rust version is s2 on?

Rust network protocol 2635 and build 168909 on Linux is the build s2 runs. To get in, your game needs the same protocol; Steam applies the update.

Is s2 up, and how often does it stay up?

Reading: offline. s2 last answered 12 hours ago. Reading: 10% uptime over the last 7 full days. It was up 16 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

How is s2 configured, and what rules are in force?

No gather rate appears in the name: s2. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is off. That is Valve's anti-cheat.

What map is s2 on?

The game generates a procedural map for s2.

How to join

How do you connect to s2?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

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.