Working its way up from the back of the class: #15,948 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 761 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 72% of all ranked servers, and #510 of the trio servers (top 85%). Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
You'll find no region listed by VOEVODIN X3. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 195.49.209.52:28025.
Is VOEVODIN X3 up, and how steady is its uptime?
At this moment, VOEVODIN X3 is offline; the last time it was seen was 21 days 23 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 7 October 2026.
What Rust version is VOEVODIN X3 on?
You will find VOEVODIN X3 on Rust network protocol 2634 and build 166652, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does VOEVODIN X3 reset?
VOEVODIN X3 has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 22 days 14 hours.
Player numbers
Where does VOEVODIN X3 place in the wider field of Rust servers?
Over the last seven days, VOEVODIN X3 has #15,948 for player hours, in the top 72% of all ranked servers. In the trio group, it ranks #510.
How many players does VOEVODIN X3 usually have?
The last sighting of VOEVODIN X3 was 21 days 23 hours ago, and it is offline right now.
Tags
How should you read the tags on VOEVODIN X3?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): Its slot count is 20; ts3 (Group limit): A team can hold 3 players at most; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags VOEVODIN X3 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does VOEVODIN X3 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include VOEVODIN X3: 3x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Trio; Gather rate: 3x.
Server rules
How is VOEVODIN X3 set up, and what rules does it keep?
The name of VOEVODIN X3 points to a 3x gather rate. The cap on group size is 3 players (trio). survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Can you tell me which map VOEVODIN X3 uses?
The game generates a procedural map for VOEVODIN X3.
How to join
What is the way to join VOEVODIN X3?
To connect, start Rust, press F1, and type client.connect 195.49.209.52:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2634,gmrust,cs166652,ts3,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp20
Max playersIts slot count is 20.
ts3
Group limitA team can hold 3 players at most.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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 term to build on. Strongest in momentum (D); standing is the one to work on (F).