Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO Q SRV11,634online PAX45,438playing OCC3,128with players WIPED 3H94
COMCommunity traffic
Callsign

VLD3130=

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

Online 82.162.62.12:28017 checked 6m ago

quad weekly wipes oxide
Clearance · join
Players now 1/ 50 2% full
7-day average1peak 5
Rank#3,130top 14%
Last wipe5d agoweekly schedule
Next wipe1d 14hThu 29 Oct, 23:07 UTC
Track history

Players

AveragePeak
0123409:0018:0003:0013:0022:0007:00

Hourly average and peak, UTC.

Server performance

05010015020009:0018:0003:0013:0022:0007: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 Sep2 Oct9 Oct15 Oct22 Oct28 Oct

Top 14% of all ranked servers, and #199 of the quad servers (top 24%). Ranked on player hours over the last seven days.

Flight plan

Wipe schedule

fixed weekdays
ETD · next wipe

Next wipe Thursday 29 October, 23:07 UTC, in 1d 14h.

Every Thursday at 23:07 UTC · medium confidence

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

Coming wipes

  1. 1d 14hThu 29 Oct, 23:07 UTC
  2. 8d 10hThu 5 Nov, 19:00 UTCFW
  3. 15d 14hThu 12 Nov, 23:07 UTC
  4. 22d 14hThu 19 Nov, 23:07 UTC
  5. 29d 14hThu 26 Nov, 23:07 UTC
  6. 36d 10hThu 3 Dec, 19:00 UTCFW
  7. 43d 14hThu 10 Dec, 23:07 UTC

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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 23:07 UTC5d ago 5 – running 1
Thu 15 Oct, 23:07 UTC12d ago 3 held half 7 days 0
Thu 8 Oct, 23:07 UTC19d ago 3 halved by day 6 7 days 0
Thu 1 Oct, 18:46 UTC FW26d 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01COM
    Callsign WRB015NA · quad · weekly · 52 on average WARBANDITS.GG |Solo/Duo/Trio/Quad|Weekly| JUST WIPED
    Players 46/200
  2. 02COM
    Callsign SRV017EA · quad · weekly · 21 on average 『小宇宙』10.27号/新开/四人服/萌新服
    Players 1/200
  3. 03COM
    Callsign SRV017EA · quad · weekly · 19 on average 『次空间』10.28号/14:00新开/四人服/萌新服
    Players 139/200
  4. 04COM
    Callsign SRV017EA · quad · weekly · 13 on average 小虎鲸10.25号|14点新档|四人游玩
    Players 0/200
  5. 05COM
    Callsign HNU017EU · quad · weekly · 12 on average [HUN] LOSTPARADISE.HU | Vanilla | Solo/Duo/Trio/Quad
    Players 1/200
  6. 06COM
    Callsign LTM025SA · quad · weekly · 9 on average [LATAM] VAINILLA Solo/Duo/Trio/Quad | 26/10 Full Wipe
    Players 0/200
ATIS · this server

Quick answers

From the figures on this page.

Tags

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

Community servers, no tags — the Rust Tracker lists that include Vladivostok [24/7] Server #2 [Classic]. It comes up under these filters 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.

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

Listed for the server browser to read, Vladivostok [24/7] Server #2 [Classic] publishes these tags: gmrust (Game mode): Survival as standard Rust plays; mp50 (Max players): Capacity: 50 slots; ts4 (Group limit): Team limit: 4; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): Region code: not set; ^w (Weekly): A weekly wipe; ^o (Oxide): A plugin framework runs here: Oxide (uMod). The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Schedule

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

The average peak across recent wipes: 4 players. The peak on the latest wipe came 38 hours after it. Recent wipes kept the crowd above half the peak until the next wipe 33% of the time. In the other cases, half the peak was lost by day 5.

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

Wipe rhythm at Vladivostok [24/7] Server #2 [Classic]: every Thursday at 23:07 UTC. Thursday 29 October at 23:07 UTC is when the next wipe falls due. 5 days 9 hours since this world was made. A weekly wipe schedule is published in its tags.

Server Details

Is Vladivostok [24/7] Server #2 [Classic] up, and how does its uptime hold?

Tracking shows Vladivostok [24/7] Server #2 [Classic] online as of now. About 12 hours ago it restarted last, based on reported uptime. 100% uptime over the last 7 full days, with 168 of 168 hours up. First contact for Rust Tracker: 26 September 2026.

Which Rust build is Vladivostok [24/7] Server #2 [Classic] running?

Rust network protocol 2635 and build 168909 on Linux is what Vladivostok [24/7] Server #2 [Classic] runs. Steam updates it for you; your game must share the protocol to join.

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

Server fps held an average of 122 across the last 48 hours, never below 93. Maximum entities carried: 47,520, from buildings and deployables to everything else. Memory peaked at 1,930 MB. A climbing entity count and low fps are what register as lag for players.

What location is Vladivostok [24/7] Server #2 [Classic] hosted in?

Nothing on region from Vladivostok [24/7] Server #2 [Classic]; none is published. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 82.162.62.12:28017.

Population

How many players are on Vladivostok [24/7] Server #2 [Classic] right now?

Vladivostok [24/7] Server #2 [Classic] is at 1 players, capacity 50. Over seven days: average 1, peak 5 players. Busiest window in 48 hours: 11:00 UTC, 4 players on average.

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

Top 14% of all ranked servers, and #3,130 on seven-day player hours: Vladivostok [24/7] Server #2 [Classic]. Position #199 among quad servers.

Settings

Which settings and rules are confirmed on Vladivostok [24/7] Server #2 [Classic]?

No gather rate appears in Vladivostok [24/7] Server #2 [Classic]'s name. The cap sits at 4 players for a group (quad). It runs survival, gather, build, raid, as the game intends. Players can raid and fight each other here. The server browser lists it under Community, as a community server. The plugin count stands at Oxide. VAC is on, Valve's anti-cheat.

Which map is confirmed for Vladivostok [24/7] Server #2 [Classic]?

Generated by the game from seed 26982, the procedural map on Vladivostok [24/7] Server #2 [Classic] measures 3,000. Look at it on RustMaps from this page: equal size and seed return the same map.

How to Join

What is the way to join Vladivostok [24/7] Server #2 [Classic]?

To connect: start Rust, press F1, enter client.connect 82.162.62.12:28017 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://m.vk.com/vlrust.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp50
Max players Capacity: 50 slots.
ts4
Group limit Team limit: 4.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking RakNet is the network layer — the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^w
Weekly A weekly wipe.

Mods and access

^o
Oxide A plugin framework runs here: 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.