Working its way up from the back of the class: #16,011 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
53/ 100
D
Moving up: up 886 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 70% of all ranked servers. 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
Next wipe Thursday 5 November, 19:00 UTC, in 8d 15h.
The 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
Where in the world is RustCorp | PvE Сервер | Ивенты | X2?
No region tag appears for RustCorp | PvE Сервер | Ивенты | X2, but the name suggests Europe. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 178.176.167.27:28015.
How reliable is RustCorp | PvE Сервер | Ивенты | X2, and is it up?
The server is down: RustCorp | PvE Сервер | Ивенты | X2 is offline now, with the last sighting 24 days 10 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 3 October 2026.
Which Rust version is RustCorp | PvE Сервер | Ивенты | X2 running?
Rust network protocol 2634 and build 166586 on Windows is what RustCorp | PvE Сервер | Ивенты | X2 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does RustCorp | PvE Сервер | Ивенты | X2 wipe, and how often?
The estimate for RustCorp | PvE Сервер | Ивенты | X2's next wipe comes from the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 25 days 8 hours. Its tags record that it wipes monthly.
Player count
What position does RustCorp | PvE Сервер | Ивенты | X2 hold in the rankings?
Over the last seven days, RustCorp | PvE Сервер | Ивенты | X2 has #16,011 for player hours, in the top 70% of all ranked servers.
What does the population on RustCorp | PvE Сервер | Ивенты | X2 look like?
It has been 24 days 10 hours since RustCorp | PvE Сервер | Ивенты | X2 was last seen, and it is offline right now.
Tags
What do RustCorp | PvE Сервер | Ивенты | X2's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166586 (Build): Build number: 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags RustCorp | PvE Сервер | Ивенты | X2 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.
Which lists and filters on Rust Server Score show RustCorp | PvE Сервер | Ивенты | X2?
Rust Server Score lists that include RustCorp | PvE Сервер | Ивенты | X2: 2x Rust servers, graded, European Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Map and rules
What settings and rules apply on RustCorp | PvE Сервер | Ивенты | X2?
The name of RustCorp | PvE Сервер | Ивенты | X2 points to a 2x gather rate. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on RustCorp | PvE Сервер | Ивенты | X2?
A procedural map, generated by the game, is what RustCorp | PvE Сервер | Ивенты | X2 runs.
Connecting
How do you get onto RustCorp | PvE Сервер | Ивенты | X2?
Enter client.connect 178.176.167.27:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^m,^p,gmrust,cs166586,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166586
BuildBuild number: 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).