Skip to the page
RUST ANALYTICS
LIVE32,953PLY11,462SRV
QUOTE 157.85.95.155:20635 Offline checked 10d ago

Battle Rust | Vanilla+ | 48h Wipe

vanillamoddedoxide
Players · last
0/ 75
n/a24h
0% full
Players · 24 hourshourly average, then now · dashed: 24 hours ago
No hourly readings in the last 24 hours.
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
0/ 75
0% full
Change · 24h
n/a
no reading a day ago
7-day average
0
peak –
Rank
#15,993
top 70%
Rank · 7d ago
#8,040
7953 places down
Last wipe
12d ago
no schedule published
Next wipe
–
no rhythm it keeps
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
0
player hours, last seven days
Map
1300
Procedural Map · seed 7562
First seen
13 Sep 2026
no hostname published

Players

No hourly history yet.

Hourly average and peak, UTC.

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep28 Sep2 Oct6 Oct10 Oct

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

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
2 days
between real wipes
on rhythm
33%
of its recent wipes
wipe-day peak
6
players, last three wipes
crowd held
0%
else halves by day 1.5

The first 48 hours of its last wipes

Thu 1 OctFri 18 SepThu 17 Sep
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 20 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 17:37 UTC FW12d ago 1 – running 0
Fri 18 Sep, 08:55 UTC25d ago 1 halved by day 2 13.4 days 0
Thu 17 Sep, 14:00 UTC26d ago 15 – 0.8 days 1
Tue 15 Sep, 13:38 UTC28d ago 24 halved by day 1 2 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1ShockRust | Blue | NoLimitno group limit · 128 on average27/300−26−49.5%
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average27/245−16−37.1%
3МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average93/100+2+1.9%
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 85 on average8/1000−8−48.4%
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average1/1000−6−86.0%
6404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 74 on average12/700−32−72.9%

Quick answers

from the figures on this page

Rules & Settings

What settings and rules are in place on Battle Rust | Vanilla+ | 48h Wipe?

No gather rate appears in the name of Battle Rust | Vanilla+ | 48h Wipe. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. Its self-description is vanilla: rust as Facepunch ships it: rates, kits and rules unchanged. VAC, Valve's anti-cheat, is enabled.

What is the current map on Battle Rust | Vanilla+ | 48h Wipe?

The map on Battle Rust | Vanilla+ | 48h Wipe is procedural, size 1,300, with seed 7562, and generated by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.

Population

What is the rank of Battle Rust | Vanilla+ | 48h Wipe?

For the last seven days, Battle Rust | Vanilla+ | 48h Wipe holds rank #15,993 on player hours, in the top 70% of all ranked servers.

How full is Battle Rust | Vanilla+ | 48h Wipe?

At present, Battle Rust | Vanilla+ | 48h Wipe is offline; the last sighting was 10 days 19 hours ago.

Wipe Frequency

What happens on wipe day at Battle Rust | Vanilla+ | 48h Wipe?

The average peak across its recent wipes is 6 players. On the latest wipe, 20 hours after the wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Below half by day 1.5 is where the crowd fell when it did not hold.

When does Battle Rust | Vanilla+ | 48h Wipe schedule its wipes?

Battle Rust | Vanilla+ | 48h Wipe wipes at times that do not follow a pattern, so no next wipe can be predicted. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. Its world now is 12 days 11 hours old.

Server Info

What is the server location for Battle Rust | Vanilla+ | 48h Wipe?

No region is published by Battle Rust | Vanilla+ | 48h Wipe. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 157.85.95.155:20635.

Battle Rust | Vanilla+ | 48h Wipe is on which Rust version?

The build is Rust network protocol 2634 and build 166494 on Linux, running on Battle Rust | Vanilla+ | 48h Wipe. Your game needs the same protocol to get in; Steam takes care of the update.

Is Battle Rust | Vanilla+ | 48h Wipe up, and how consistent is its uptime?

Offline at this moment: Battle Rust | Vanilla+ | 48h Wipe. Last seen 10 days 19 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. First sighting by Rust Analytics: 13 September 2026.

Tags & Filters

How should you interpret the tags on Battle Rust | Vanilla+ | 48h Wipe?

The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp75 (Max players): Capacity: 75 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): To join, your game needs protocol 2634; cs166494 (Build): It runs build 166494; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): Region code: none set; ^v (Vanilla): Rust as Facepunch ships it: rates, kits and rules unchanged; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which Battle Rust | Vanilla+ | 48h Wipe publishes. The top of this page and the tags both show its players now, its queue and when its world was made.

On Rust Analytics, which lists and filters feature Battle Rust | Vanilla+ | 48h Wipe?

On Rust Analytics, Battle Rust | Vanilla+ | 48h Wipe matches these lists: Modded Rust servers. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Connection

What is the process to join Battle Rust | Vanilla+ | 48h Wipe?

The console route: start Rust, press F1, enter client.connect 157.85.95.155:20635. The page's Launch Rust button opens Rust through Steam and connects you instead. You can reach its website at https://discord.com/invite/YYCm58Zrs.

Server tags

what each one means

Published as mp75,ptrak,$r?,v2634,^v,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode Rust's standard survival mode.
mp75
Max players Capacity: 75 slots.
ts8
Group limit At the game default, teams hold up to 8.
v2634
Protocol To join, your game needs protocol 2634.
cs166494
Build It runs build 166494.
ptrak
Networking The standard network layer, RakNet.
$r?
Region code Region code: none set.

Difficulty

^v
Vanilla Rust as Facepunch ships it: rates, kits and rules unchanged.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

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.