RUST ZERG LIFEClan war room · live
Quadmax 4
Deployment dossierOnline

Vladivostok [24/7] Server #2 [Classic]

82.162.62.12:28017 checked 11m ago

quad weekly wipes oxide
Deploy
Zerg meter0%empty
0/50 troops
7-day average1
peak 5
Rank#4,009
top 18%
Last wipe4d ago
weekly schedule
Next wipe · H-hour2d 1h
Thu 15 Oct, 23:07 UTC

Players

AveragePeak
0246822:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

05010015020022:0007:0016:0002:0011:0020: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 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep29 Sep3 Oct6 Oct10 Oct13 Oct

Top 18% of all ranked servers, and #259 of the quad servers (top 32%). Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag

Next wipe Thursday 15 October, 23:07 UTC, in 2d 1h. Its weekly schedule tag · low confidence

usual gap7.2 days
between real wipes
wipe-day peak4
players, last three wipes
crowd held0%
else halves by day 4

Coming wipes

2d 1hThu 15 Oct, 23:07 UTC
9d 1hThu 22 Oct, 23:07 UTC
16d 1hThu 29 Oct, 23:07 UTC
22d 21hThu 5 Nov, 19:00 UTCFW
30d 1hThu 12 Nov, 23:07 UTC
37d 1hThu 19 Nov, 23:07 UTC
44d 1hThu 26 Nov, 23:07 UTC

The first 48 hours of its last wipes

Thu 8 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 10 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 23:07 UTC4d ago 3 – running 0
Thu 1 Oct, 18:46 UTC FW12d ago 4 halved by day 4 7.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
Quadmax 4
[LATAM] VAINILLA Solo/Duo/Trio/Quad | 10/10 Full Wipe SA · quad · weekly · 92 on average
16/200
Quadmax 4
WARBANDITS.GG |Solo/Duo/Trio/Quad|Weekly| JUST WIPED NA · quad · weekly · 39 on average
56/200
Quadmax 4
[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours EA · quad · weekly · 29 on average
2/165
Quadmax 4
『小宇宙』10.13号/新开/四人服/萌新服 EA · quad · weekly · 20 on average
0/200
Quadmax 4
『次空间』10.12号/新开/四人服/萌新服 EA · quad · weekly · 16 on average
0/200
Quadmax 4 23/100

Quick answers

from the figures on this page

Map and rules

What settings does Vladivostok [24/7] Server #2 [Classic] run?

No gather rate appears in the name Vladivostok [24/7] Server #2 [Classic]. 4 players is the group cap (quad). It runs survival, gather, build, raid: the regular game. Raiding and fighting other players are allowed. The server browser lists it under Community. The plugins it runs number Oxide. VAC is on, Valve's anti-cheat.

What is the map on Vladivostok [24/7] Server #2 [Classic]?

Size 3,000, seed 26982, generated by the game: the procedural map on Vladivostok [24/7] Server #2 [Classic]. You can view it on RustMaps from this page, since the same size and seed give the same map.

Player count

What is the population like on Vladivostok [24/7] Server #2 [Classic]?

Right now, 0 players are on Vladivostok [24/7] Server #2 [Classic], which has 50 slots. Its weekly average is 1 players and its highest point was 5. In the last two days, the peak hour was 03:00 UTC, with an average of 4 players.

What is Vladivostok [24/7] Server #2 [Classic]'s ranking?

For player hours over the last week, Vladivostok [24/7] Server #2 [Classic] is #4,009, which puts it in the top 18% of all ranked servers. In the quad category, it ranks #259.

Tags and filters

How should you read the tags on Vladivostok [24/7] Server #2 [Classic]?

What the game's server browser gets from Vladivostok [24/7] Server #2 [Classic] is this tag list: gmrust (Game mode): Standard survival gameplay; mp50 (Max players): It holds 50 players; ts4 (Group limit): Each team can have up to 4 players; v2634 (Protocol): You'll need protocol 2634 on your game to join; cs167781 (Build): It runs build 167781; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code is set; ^w (Weekly): The server wipes weekly; ^o (Oxide): Plugins run through Oxide (uMod). Also in the tags: its players now, its queue and the time its world was made, and the top of this page shows them.

Where does Vladivostok [24/7] Server #2 [Classic] appear in Rust Zerg Life lists?

Rust community servers for clans: that is where you will find Vladivostok [24/7] Server #2 [Classic] among the Rust Zerg Life rankings. Under these filters it shows on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Weekly ^w and Oxide ^o; Group limit: Quad; Wipe schedule: Weekly; Last wipe: In the last week.

Server details

What is the uptime and reliability of Vladivostok [24/7] Server #2 [Classic]?

Vladivostok [24/7] Server #2 [Classic] is up and running as you read this. The uptime figure it gives suggests it restarted around 1 hours ago. Over the last 7 full days, uptime was 100%: 168 hours up out of 168. Its first appearance in Rust Zerg Life records is 26 September 2026.

How well does Vladivostok [24/7] Server #2 [Classic] perform?

Server fps held an average of 116 for the last 48 hours, with a minimum of 46. It reached a maximum of 46,234 entities, covering buildings, deployables and the rest of the world. Memory use peaked at 1,893 MB. A climbing entity count and low fps are the source of the lag players feel.

What Rust version is Vladivostok [24/7] Server #2 [Classic] on?

The server Vladivostok [24/7] Server #2 [Classic] runs Rust network protocol 2634 and build 167781 with Linux as its operating system. The protocol must match for you to join, and Steam will update your game to that protocol.

What location does Vladivostok [24/7] Server #2 [Classic] use?

No region is published by Vladivostok [24/7] Server #2 [Classic]. The location shown by Rust Zerg Life is what a server says; it does not check where the machine stands. Connect to it at 82.162.62.12:28017.

Wipe schedule

What happens on wipe day on Vladivostok [24/7] Server #2 [Classic]?

At their busiest, its recent wipes drew an average of 4 players. On the latest wipe, 10 hours after the wipe, the crowd hit its peak. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. Otherwise, it slipped below half by day 4.

When does Vladivostok [24/7] Server #2 [Classic] wipe?

With too few wipes recorded to confirm Vladivostok [24/7] Server #2 [Classic]'s schedule, the prediction comes from its tag. It is due to wipe next on Thursday 15 October at 23:07 UTC. 4 days 22 hours ago is when its present world was created. Its tags carry a weekly wipe schedule.

Connect

How can I connect to Vladivostok [24/7] Server #2 [Classic]?

Enter client.connect 82.162.62.12:28017 in the F1 console. Another way: use Launch Rust on this page, which opens Rust through Steam and connects you. For more, visit its website: https://m.vk.com/vlrust.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,^w,gmrust,cs167781,ts4,^o

Game

gmrust
Game mode Standard survival gameplay.
mp50
Max players It holds 50 players.
ts4
Group limit Each team can have up to 4 players.
v2634
Protocol You'll need protocol 2634 on your game to join.
cs167781
Build It runs build 167781.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly The server wipes weekly.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).

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.