RUST METRICSFlight deck · live data
Data live Servers11,704 Players61,057 Populated3,258 Fresh wipes 3 h178 Scan5 min
‹ All servers82.162.62.12:28017
Online Full Queue Fresh wipe Wipe due No query

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

Online 82.162.62.12:28017 checked 13m ago

quad weekly wipes oxide
COM 1 · connect

Server instruments

last reading Thu 23:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 112 SERVER FPS

Server fps

48 h low 58 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 47,459 ×1000

Entities

48 h range 45,190–47,840 · memory 1,598 MB
1239 ET SINCE RESTART 03:54

Uptime

3 h 54 min since its last restart, at the last reading
7-day average1peak 5
Rank#2,957top 13%
Last wipe1h agoweekly schedule
Next wipe6d 18hThu 5 Nov, 19:00 UTC FW
Memory1,598MB48 h peak 3 players
REC 1

Players

AveragePeak
0123401:0010:0020:0005:0014:0023:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020001:0010:0020:0005:0014:0023: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep3 Oct9 Oct16 Oct22 Oct29 Oct

Top 13% of all ranked servers, and #185 of the quad servers (top 22%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

fixed weekdays

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

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak4players, last three wipes
crowd held25%else halves by day 6

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 18hFW
  2. WPT 2Thu 12 Nov, 23:07 UTC13d 22h
  3. WPT 3Thu 19 Nov, 23:07 UTC20d 22h
  4. WPT 4Thu 26 Nov, 23:07 UTC27d 22h
  5. WPT 5Thu 3 Dec, 19:00 UTC34d 18hFW
  6. WPT 6Thu 10 Dec, 23:07 UTC41d 22h

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 5, 38 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 23:07 UTC1h ago – – running 0
Thu 22 Oct, 23:07 UTC7d ago 5 – – 1
Thu 15 Oct, 23:07 UTC14d ago 3 held half 7 days 0
Thu 8 Oct, 23:07 UTC21d ago 3 halved by day 6 7 days 0
Thu 1 Oct, 18:46 UTC FW28d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

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

The busiest point of its recent wipes drew 4 players on average. After the latest wipe, numbers topped out at 38 hours. The crowd stayed above half that peak until the next wipe in 25% of its recent wipes. By day 6 it fell below half when it didn't.

How often does Vladivostok [24/7] Server #2 [Classic] wipe, and when?

The wipe rhythm of Vladivostok [24/7] Server #2 [Classic] is every Thursday at 23:07 UTC. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world in play was created 1 hours ago. Its tags carry a weekly wipe schedule.

Lists and filters

Which tags does Vladivostok [24/7] Server #2 [Classic] carry, and what do they mean?

Tags published by Vladivostok [24/7] Server #2 [Classic], read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts4 (Group limit): Teams are capped at 4; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^w (Weekly): Wipe cycle: weekly; ^o (Oxide): Plugin framework in use: Oxide (uMod). Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Vladivostok [24/7] Server #2 [Classic]?

Rust Metrics lists featuring Vladivostok [24/7] Server #2 [Classic]: Rust community servers: live readings. Reading: server list filters. It comes up under 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 24 hours.

Player count

Where does Vladivostok [24/7] Server #2 [Classic] sit in the rankings?

Ranking for Vladivostok [24/7] Server #2 [Classic]: #2,957 on seven-day player hours, top 13% of all ranked servers. Among servers in quad, it stands at #185.

What player count does Vladivostok [24/7] Server #2 [Classic] carry?

Current headcount on Vladivostok [24/7] Server #2 [Classic]: 0 players, 50 slots available. Seven-day check: 1 players on average. Peak reading: 5. The last 48 hours peaked at 05:00 UTC, averaging 3 players at that hour.

Server

Which location does Vladivostok [24/7] Server #2 [Classic] run from?

No region comes from Vladivostok [24/7] Server #2 [Classic]. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 82.162.62.12:28017.

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

Rust network protocol 2635 and build 168909 on Linux is the build Vladivostok [24/7] Server #2 [Classic] runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: 115 server fps on average across the last 48 hours. It never dropped below 58. Reading: 47,840 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 2,015 MB. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on Vladivostok [24/7] Server #2 [Classic], and is it online?

Vladivostok [24/7] Server #2 [Classic] reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 3 hours ago. Uptime for the last 7 full days: 143 of 168 hours, or 85%. Check: first contact. Rust Metrics logged it on 26 September 2026.

Settings and map

How is Vladivostok [24/7] Server #2 [Classic] configured, and what rules are in force?

No gather rate appears in the name: Vladivostok [24/7] Server #2 [Classic]. Check: group limit. 4 players, under the name quad. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

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

Size 3,000 and seed 26982: the game generates the procedural map on Vladivostok [24/7] Server #2 [Classic] from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How can you get onto Vladivostok [24/7] Server #2 [Classic]?

To join: start Rust, press F1 and type client.connect 82.162.62.12:28017. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://m.vk.com/vlrust.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^w,gmrust,cs168909,ts4,^o

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts4
Group limit Teams are capped at 4.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly Wipe cycle: weekly.

Mods and access

^o
Oxide Plugin framework in use: 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.