StatusLive Servers online11,646 Players42,725 Populated3,027 Wiped · 3 h89 Interval5 min Date29 OCT 2026

DWG RG-S15993Server sheetchecked 25d ago

Battle Rust | Vanilla+ | 48h Wipe

Offline 157.85.95.155:20635 checked 25d ago

vanillamoddedoxide
Connect
Players now 0/ 75 0% full
7-day average0peak –
Rank#15,993top 70%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on Battle Rust | Vanilla+ | 48h Wipe
Fig. 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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Fig. 2FPS, entities and memory
Fig. 3

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.

Fig. 3Rank on player hours, daily
Schedule

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 gap2 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak6players, last three wipes
crowd held0%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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

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

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 150 on average
100 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
129 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
125 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
46 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
4 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
19 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

What uptime is recorded for Battle Rust | Vanilla+ | 48h Wipe, and is it up?

Last seen 25 days 22 hours ago; right now Battle Rust | Vanilla+ | 48h Wipe is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. On 13 September 2026 is when Rust Graphs first saw it.

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

A region is not published by Battle Rust | Vanilla+ | 48h Wipe. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 157.85.95.155:20635.

What Rust version is recorded for Battle Rust | Vanilla+ | 48h Wipe?

The platform is Linux and the version is Rust network protocol 2634 and build 166494 on Battle Rust | Vanilla+ | 48h Wipe. The same protocol is required for joining, and Steam updates your game to it.

Counts

What does the population history show for Battle Rust | Vanilla+ | 48h Wipe?

The latest refresh records Battle Rust | Vanilla+ | 48h Wipe as offline, last seen 25 days 22 hours ago.

Against other Rust servers, where is Battle Rust | Vanilla+ | 48h Wipe placed?

Within the top 70% of all ranked servers: Battle Rust | Vanilla+ | 48h Wipe at #15,993 for player hours, seven days recorded.

Wipe times

What is recorded on Battle Rust | Vanilla+ | 48h Wipe on wipe day?

The recent wipes averaged a busiest count of 6 players. At 20 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. By day 1.5 the crowd had fallen below half on the wipes where it did not hold.

What wipe schedule has been recorded for Battle Rust | Vanilla+ | 48h Wipe?

Battle Rust | Vanilla+ | 48h Wipe wipes at times that follow no pattern, so no next wipe can be predicted. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. 27 days 14 hours ago the current world was made.

Settings

What settings and rules apply on Battle Rust | Vanilla+ | 48h Wipe?

The name of Battle Rust | Vanilla+ | 48h Wipe records no gather rate. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. Its own label is vanilla, meaning rates, kits and rules are unchanged from Facepunch's release. Anti-cheat: VAC, from Valve, is on.

On which map is Battle Rust | Vanilla+ | 48h Wipe played?

Battle Rust | Vanilla+ | 48h Wipe runs a procedural map of size 1,300 with seed 7562, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.

Filters

On Rust Graphs, which lists and filters contain Battle Rust | Vanilla+ | 48h Wipe?

On Rust Graphs, Battle Rust | Vanilla+ | 48h Wipe is placed in these lists: Modded Rust servers. These filters on the server list return it: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meaning is attached to each tag on Battle Rust | Vanilla+ | 48h Wipe?

The game's server browser reads these tags from Battle Rust | Vanilla+ | 48h Wipe: gmrust (Game mode): Standard survival, as Rust plays; mp75 (Max players): The slot count is 75; ts8 (Group limit): The default team size of 8 applies; v2634 (Protocol): To join, your game must be on protocol 2634; cs166494 (Build): 166494 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^v (Vanilla): Rates, kits and rules are unchanged from Facepunch's release; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Joining the server

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

Connect with client.connect 157.85.95.155:20635: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://discord.com/invite/YYCm58Zrs.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp75
Max players The slot count is 75.
ts8
Group limit The default team size of 8 applies.
v2634
Protocol To join, your game must be on protocol 2634.
cs166494
Build 166494 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Difficulty

^v
Vanilla Rates, kits and rules are unchanged from Facepunch's release.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

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.

KeyTag string decoded