Working its way up from the back of the class: #15,993 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
25/ 100
F
Lost ground: down 7,953 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·WW··
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 1, 20 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 17:37 UTCFW27d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does Battle Rust | Vanilla+ | 48h Wipe sit?
No region is published for Battle Rust | Vanilla+ | 48h Wipe. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 157.85.95.155:20635.
How dependable is Battle Rust | Vanilla+ | 48h Wipe, and is it online at the moment?
You cannot join now: Battle Rust | Vanilla+ | 48h Wipe is offline, last seen 25 days 16 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Battle Rust | Vanilla+ | 48h Wipe running?
Rust network protocol 2634 and build 166494 on Linux is what Battle Rust | Vanilla+ | 48h Wipe runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Battle Rust | Vanilla+ | 48h Wipe wipe, and how often?
Battle Rust | Vanilla+ | 48h Wipe wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 27 days 8 hours.
What should you expect from wipe day on Battle Rust | Vanilla+ | 48h Wipe?
Across its recent wipes, the busiest moments averaged 6 players. The crowd on the latest wipe was largest 20 hours after it began. Half the peak held until the next wipe in 0% of its recent wipes. Day 1.5 is when it sank below half in the wipes that did not hold.
Player count
Where does Battle Rust | Vanilla+ | 48h Wipe sit among Rust servers?
Over the last seven days, Battle Rust | Vanilla+ | 48h Wipe has #15,993 for player hours, in the top 70% of all ranked servers.
How many players does Battle Rust | Vanilla+ | 48h Wipe usually have?
The last sighting of Battle Rust | Vanilla+ | 48h Wipe was 25 days 16 hours ago, and it is offline right now.
Lists and filters
What do Battle Rust | Vanilla+ | 48h Wipe's tags stand for?
The game's browser takes its cue from the tags Battle Rust | Vanilla+ | 48h Wipe has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp75 (Max players): 75 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Battle Rust | Vanilla+ | 48h Wipe?
These Rust Server Score lists count Battle Rust | Vanilla+ | 48h Wipe among them: Modded Rust servers, graded. 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.
Rules and settings
What settings and rules apply on Battle Rust | Vanilla+ | 48h Wipe?
You will find no gather rate in the name of Battle Rust | Vanilla+ | 48h Wipe. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Battle Rust | Vanilla+ | 48h Wipe uses?
A procedural map of size 1,300 and seed 7562, generated by the game, is what Battle Rust | Vanilla+ | 48h Wipe runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto Battle Rust | Vanilla+ | 48h Wipe?
To connect, start Rust, press F1, and type client.connect 157.85.95.155:20635. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/YYCm58Zrs.
Server tags
what each one means
Published asmp75,ptrak,$r?,v2634,^v,gmrust,cs166494,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp75
Max players75 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under 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.
A term to build on. Strongest in standing (F); wipes are the one to work on (F).