On the class lists: C− (55), with population over 48 hours and no performance mark.
Players now2/ 504% full
7-day average1peak 5
Rank#3,000top 14%
Last wipe5d agoweekly schedule
Next wipe1d 3hThu 29 Oct, 23:07 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 1 of 50 on average. Plenty of space to grow.
Standingrank on player hours
86/ 100
A−
Holds a respectable place: #3,000 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 123 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
55/ 100
C−
Moving up: up 301 places this week.
A fair term, with more to come.
Strongest in performance (A+); population is 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 14% of all ranked servers, and #189 of the quad servers (top 23%). Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
···W···
···W···
···W···
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Thursday 29 October, 23:07 UTC, in 1d 3h.
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
1d 3hThu 29 Oct, 23:07 UTC
7d 23hThu 5 Nov, 19:00 UTCFW
15d 3hThu 12 Nov, 23:07 UTC
22d 3hThu 19 Nov, 23:07 UTC
29d 3hThu 26 Nov, 23:07 UTC
35d 23hThu 3 Dec, 19:00 UTCFW
43d 3hThu 10 Dec, 23:07 UTC
The first 48 hours of its last wipes
Thu 22 OctThu 15 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 5, 38 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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 UTCFW27d 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
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is Vladivostok [24/7] Server #2 [Classic]?
No region is published for Vladivostok [24/7] Server #2 [Classic]. Rust Server Score takes the server's word for its location and does not trace the hardware. 82.162.62.12:28017 is the address to use.
How reliable is Vladivostok [24/7] Server #2 [Classic], and is it up?
You can join now: Vladivostok [24/7] Server #2 [Classic] is online. According to its reported uptime, the last restart was about 20 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. The first sighting by Rust Server Score was on 26 September 2026.
How well does Vladivostok [24/7] Server #2 [Classic] run?
It averaged 123 server fps over the last 48 hours, with a low of 93. Up to 47,632 entities were in the world, covering buildings, deployables and the rest. Up to 2,015 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is Vladivostok [24/7] Server #2 [Classic] on?
You will find Vladivostok [24/7] Server #2 [Classic] on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Vladivostok [24/7] Server #2 [Classic] wipe its map?
The wipe rhythm on Vladivostok [24/7] Server #2 [Classic] is every Thursday at 23:07 UTC. It is due to wipe next on Thursday 29 October at 23:07 UTC. The world it runs now was created 5 days 20 hours. The tags carry a weekly wipe schedule.
What should you expect from wipe day on Vladivostok [24/7] Server #2 [Classic]?
Across its recent wipes, the busiest moments averaged 4 players. The crowd on the latest wipe was largest 38 hours after it began. Half the peak held until the next wipe in 33% of its recent wipes. In the other wipes it slipped under half by day 5.
Player count
Where does Vladivostok [24/7] Server #2 [Classic] place in the wider field of Rust servers?
In the top 14% of all ranked servers, Vladivostok [24/7] Server #2 [Classic] sits at #3,000 for player hours over the last seven days. In the quad group, it ranks #189.
Is Vladivostok [24/7] Server #2 [Classic] a busy server?
Vladivostok [24/7] Server #2 [Classic] is showing 2 players right now, with 50 slots in total. The seven-day average is 1 players, with a peak of 5. Over the last 48 hours, the peak hour was 11:00 UTC, averaging 4 players.
Tags
What do Vladivostok [24/7] Server #2 [Classic]'s tags stand for?
The game's browser takes its cue from the tags Vladivostok [24/7] Server #2 [Classic] has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 slots; ts4 (Group limit): A team can hold 4 players at most; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^w (Weekly): A wipe happens every week; ^o (Oxide): Oxide (uMod) provides the plugin framework here. 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 Vladivostok [24/7] Server #2 [Classic]?
These Rust Server Score lists count Vladivostok [24/7] Server #2 [Classic] among them: Best community servers, graded. It shows under the following 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.
Map and rules
Which rules does Vladivostok [24/7] Server #2 [Classic] enforce, and what are its settings?
You will find no gather rate in the name of Vladivostok [24/7] Server #2 [Classic]. The cap on group size is 4 players (quad). It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Vladivostok [24/7] Server #2 [Classic] uses?
A procedural map of size 3,000 and seed 26982, generated by the game, is what Vladivostok [24/7] Server #2 [Classic] 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 Vladivostok [24/7] Server #2 [Classic]?
To connect, start Rust, press F1, and type client.connect 82.162.62.12:28017. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://m.vk.com/vlrust.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^w,gmrust,cs168909,ts4,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 slots.
ts4
Group limitA team can hold 4 players at most.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).