At press time 11,840 servers80,134 players159 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 2,993

Bunker 400 - Russian Server

Online 95.154.74.92:28015 checked 11m ago

Bunker 400 - Russian Server is a Rust server. At the last count it had 3 players of a possible 400; over the past week it averaged 1, with a peak of 6. It stands at No. 2,993 of the ranked servers, the top 14%. It last wiped 26d ago, on a monthly schedule, and the next wipe is expected on Thursday 5 November, with the force wipe. Its own tags class it as vanilla, oxide.

§ 1Attendance

AveragePeak
0246822:0007:0016:0001:0010:0019:00

Hourly average and peak, UTC.

§ 2Performance

025507510022:0007:0016:0001:0010:0019: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.

§ 3Standingthe rank, daily · 1 is best

RankRank in region
11k2k3k4k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

§ 4The wipe scheduleforce wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 21h. The force wipe · high confidence

The rhythm
Usual gap4.1 days

between real wipes

Wipe-day peak8

players, last three wipes

Crowd held100%

of its cycles kept half the crowd

Coming wipes
Date, UTCHence
Thu 5 Nov, 19:00 FW8d 21h
Thu 3 Dec, 19:00 FW36d 21h

The first 48 hours of its last wipes

Mon 5 OctThu 1 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 8, 14 hours in.

§ 5The record of wipesnewest first

WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 21:32 UTC21d ago 8 – running 1
Thu 1 Oct, 19:09 UTC FW26d ago 7 held half 4.1 days 2

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.

§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 Rustoria.co - EU East Long392/450 EU · groups of 12+ · monthly · 315 on average
  2. 2 Rusty Moose |EU Monthly|240/275 EU · groups of 12+ · monthly · 210 on average
  3. 3 [EU East] Facepunch 4173/350 EU · groups of 8+ · monthly · 187 on average
  4. 4 [EU] Facepunch 1260/400 EU · groups of 8+ · monthly · 153 on average
  5. 5 Rustopia.gg - US Large134/200 NA · groups of 16+ · monthly · 137 on average
  6. 6 Magic Rust — Long | Kлaccикa x1 | Pyccкий139/300 EU · groups of 150+ · 1x · monthly · 132 on average

§ 7Questions answeredfrom the figures in this entry

Server record

On which Rust version does Bunker 400 - Russian Server operate?

The server Bunker 400 - Russian Server is on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must be on the same protocol; Steam handles the update.

What does uptime look like on Bunker 400 - Russian Server, and is it up?

Bunker 400 - Russian Server currently answers as online. A restart came about 19 hours ago, by the server's own uptime figure. Of note: 168 of 168 hours up in the last 7 full days, or 100% of the time. Its earliest entry at Rust Server Stats is dated 13 September 2026.

Does Bunker 400 - Russian Server hold a steady frame?

For the last 48 hours the average was 65 server fps, with a low of 43. Buildings, deployables and the rest brought the entity count to a high of 150,707. Up to 5,271 MB of memory was used. What players feel as lag: fps running low and entities climbing.

What is the location of Bunker 400 - Russian Server?

No region is published by Bunker 400 - Russian Server. Where the machine stands is not looked up by Rust Server Stats; it shows where a server says it is. At 95.154.74.92:28015 stands the address.

The rules and map

What map is in use on Bunker 400 - Russian Server?

Bunker 400 - Russian Server runs a procedural map, generated by the game, of size 5,000 with seed 346176. Because size and seed fix the map, it can be viewed on RustMaps from here.

What settings and rules does Bunker 400 - Russian Server run?

Nothing in the name of Bunker 400 - Russian Server gives a gather rate. The group limit is 8 players, the game's default. Play is survival, gather, build and raid: the standard game. Combat and raiding between players are permitted. It appears under Community in the server browser and is a community server. Oxide plugins are in use. The server describes itself as vanilla: unchanged rates, kits and rules: Facepunch's own game. The VAC anti-cheat from Valve is active.

Population

What population does Bunker 400 - Russian Server carry?

At the latest count Bunker 400 - Russian Server has 3 players, with 400 slots in total. Averaged across seven days, 1 players; the peak reached 6. The busiest hour of the last 48 was 15:00 UTC, averaging 5 players.

What position does Bunker 400 - Russian Server hold among Rust servers?

The seven-day player-hour table places Bunker 400 - Russian Server at #2,993, within the top 14% of ranked servers.

The tags and lists

Bunker 400 - Russian Server sits in which Rust Server Stats lists and filters?

These are the Rust Server Stats lists that include Bunker 400 - Russian Server: Best Rust community servers and Best vanilla Rust servers. On the server list it comes up under these filters: Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Which meanings attach to the tags on Bunker 400 - Russian Server?

These tags are Bunker 400 - Russian Server's, and the game's browser reads them: gmrust (Game mode): The standard survival game; mp400 (Max players): Slot count: 400; ts8 (Group limit): Set at the game default of 8 per team; v2635 (Protocol): Protocol 2635: joining needs the same game version; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set; ^m (Monthly): One wipe a month, alongside the force wipe from Facepunch; ^v (Vanilla): Unchanged rates, kits and rules: Facepunch's own game; ^o (Oxide): Oxide (uMod), a framework for plugins, runs here. The tags also carry its current players, its queue and the date its world was made. These appear at the top of this page.

Wipe schedule

What happens on Bunker 400 - Russian Server when wipe day arrives?

Averaged over recent wipes, the crowd reached 8 at its busiest. 14 hours into the latest wipe the crowd reached its peak. Above half that peak until the next wipe: the crowd held in 100% of recent wipes.

The wipe timetable for Bunker 400 - Russian Server: what does it show?

Bunker 400 - Russian Server wipes with the force wipe alone, once a month. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe shared by every Rust server. The present world dates from 26 days 1 hours. The tags list wipes as monthly.

How to join

Which steps join Bunker 400 - Russian Server?

Join on this page with Launch Rust, which opens Rust through Steam and connects you, or open the console with F1 and enter client.connect 95.154.74.92:28015.

§ 8Key to the tagswhat each one means

Published as mp400,ptrak,$r?,v2635,^m,^v,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode The standard survival game.
mp400
Max players Slot count: 400.
ts8
Group limit Set at the game default of 8 per team.
v2635
Protocol Protocol 2635: joining needs the same game version.
cs168909
Build Build 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly One wipe a month, alongside the force wipe from Facepunch.

Difficulty

^v
Vanilla Unchanged rates, kits and rules: Facepunch's own game.

Mods and access

^o
Oxide Oxide (uMod), a framework for plugins, runs here.

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.