Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak85players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 85, 8 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 14 Sep, 08:55 UTC43d ago
85
–
running
28
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
Which region is X4C.RU — Раст Новосибирск based in?
You won't find a region tag on X4C.RU — Раст Новосибирск, but its name indicates Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 5.42.211.241:35000.
How dependable is X4C.RU — Раст Новосибирск, and is it online at the moment?
At this moment, X4C.RU — Раст Новосибирск is offline; the last time it was seen was 43 days 6 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
On what Rust version does X4C.RU — Раст Новосибирск sit?
Rust network protocol 2633 and build 163794 on Linux is what X4C.RU — Раст Новосибирск runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does X4C.RU — Раст Новосибирск wipe its map?
There are too few wipes on record for X4C.RU — Раст Новосибирск to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 43 days 14 hours.
What happens on X4C.RU — Раст Новосибирск when wipe day arrives?
The average peak on its recent wipes was 85 players. Peak numbers came 8 hours into the latest wipe.
Player numbers
Where does X4C.RU — Раст Новосибирск sit among Rust servers?
In the top – of all ranked servers, X4C.RU — Раст Новосибирск sits at #4,102 for player hours over the last seven days.
What does the population on X4C.RU — Раст Новосибирск look like?
The last sighting of X4C.RU — Раст Новосибирск was 43 days 6 hours ago, and it is offline right now.
Lists and filters
What do X4C.RU — Раст Новосибирск's tags stand for?
The game's browser takes its cue from the tags X4C.RU — Раст Новосибирск has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod). 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 Rust Server Score filters and lists feature X4C.RU — Раст Новосибирск?
Rust Server Score lists that include X4C.RU — Раст Новосибирск: European Rust servers, graded and Best community servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Players now: At least 50.
Rules and settings
What settings and rules apply on X4C.RU — Раст Новосибирск?
You will find no gather rate in the name of X4C.RU — Раст Новосибирск. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Connecting
What is the way to join X4C.RU — Раст Новосибирск?
To connect, start Rust, press F1, and type client.connect 5.42.211.241:35000. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is 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.
Not enough figures yet to write a report. Check back after a few days on the list.