Working its way up from the back of the class: #16,892 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
46/ 100
D
Slipped a little: down 1,420 places this week. Nothing a good wipe can't fix.
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.
AveragePeakWipe
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 71% 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 7d 19h.
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
EU · groups of 300+ · 2x · monthly · 151 on average
53 / 500
Quick answers
from the figures on this page
Server facts
Where in the world is КОНТОРА | 2X RU | Nolimit?
No region tag appears for КОНТОРА | 2X RU | Nolimit, but the name suggests Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 31.76.113.163:28015.
Is КОНТОРА | 2X RU | Nolimit up, and how steady is its uptime?
You cannot join now: КОНТОРА | 2X RU | Nolimit is offline, last seen 29 days 15 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 28 September 2026.
On what Rust version does КОНТОРА | 2X RU | Nolimit sit?
Rust network protocol 2633 and build 165217 on Windows is what КОНТОРА | 2X RU | Nolimit runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does КОНТОРА | 2X RU | Nolimit wipe, and how often?
The estimate for КОНТОРА | 2X RU | Nolimit's next wipe comes from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 30 days 8 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Population
Where does КОНТОРА | 2X RU | Nolimit place in the wider field of Rust servers?
In the top 71% of all ranked servers, КОНТОРА | 2X RU | Nolimit sits at #16,892 for player hours over the last seven days.
Is КОНТОРА | 2X RU | Nolimit a busy server?
The last sighting of КОНТОРА | 2X RU | Nolimit was 29 days 15 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on КОНТОРА | 2X RU | Nolimit?
The game's browser takes its cue from the tags КОНТОРА | 2X RU | Nolimit has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp300 (Max players): 300 slots are available; ts128 (Group limit): No team may go above 128; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 КОНТОРА | 2X RU | Nolimit?
Rust Server Score lists that include КОНТОРА | 2X RU | Nolimit: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Rules and settings
What settings and rules apply on КОНТОРА | 2X RU | Nolimit?
The name of КОНТОРА | 2X RU | Nolimit points to a 2x gather rate. The limit for a group is 128 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
КОНТОРА | 2X RU | Nolimit runs which map?
The game generates a procedural map for КОНТОРА | 2X RU | Nolimit.
Getting in
What is the way to join КОНТОРА | 2X RU | Nolimit?
To connect, start Rust, press F1, and type client.connect 31.76.113.163:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp300,ptrak,$r?,v2633,^m,gmrust,cs165217,ts128,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp300
Max players300 slots are available.
ts128
Group limitNo team may go above 128.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits 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).