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.
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
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
Which region is LOCAL RUST X10 | Kits | RaidBlock | WipeBlock based in?
No region is published for LOCAL RUST X10 | Kits | RaidBlock | WipeBlock. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 46.38.18.200:28015.
How reliable is LOCAL RUST X10 | Kits | RaidBlock | WipeBlock, and is it up?
You cannot join now: LOCAL RUST X10 | Kits | RaidBlock | WipeBlock is offline, last seen 39 days 22 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 19 September 2026, Rust Server Score saw it for the first time.
What Rust version is LOCAL RUST X10 | Kits | RaidBlock | WipeBlock on?
Rust network protocol 2633 and build 163794 on Windows is what LOCAL RUST X10 | Kits | RaidBlock | WipeBlock runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock wipe its map?
There are too few wipes on record for LOCAL RUST X10 | Kits | RaidBlock | WipeBlock to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 42 days 14 hours.
Player numbers
Where does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock sit among Rust servers?
In the top – of all ranked servers, LOCAL RUST X10 | Kits | RaidBlock | WipeBlock sits at #13,312 for player hours over the last seven days.
How many players does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock usually have?
It has been 39 days 22 hours since LOCAL RUST X10 | Kits | RaidBlock | WipeBlock was last seen, and it is offline right now.
Tags
What is meant by the tags on LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
You'll see LOCAL RUST X10 | Kits | RaidBlock | WipeBlock tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): 20 slots are available; ts4 (Group limit): A team can hold 4 players at most; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^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 in the browser, which picks them up from the server. 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 LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
These Rust Server Score lists count LOCAL RUST X10 | Kits | RaidBlock | WipeBlock among them: 10x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Quad; Gather rate: 10x.
Map and rules
What settings and rules apply on LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
The name of LOCAL RUST X10 | Kits | RaidBlock | WipeBlock points to a 10x gather rate. You can have up to 4 players in a group (quad). You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map LOCAL RUST X10 | Kits | RaidBlock | WipeBlock uses?
A procedural map, generated by the game, is what LOCAL RUST X10 | Kits | RaidBlock | WipeBlock runs.
Getting in
What is the way to join LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
Enter client.connect 46.38.18.200: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 asmp20,ptrak,$r?,v2633,gmrust,cs163794,ts4,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max players20 slots are available.
ts4
Group limitA team can hold 4 players at most.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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.
Not enough figures yet to write a report. Check back after a few days on the list.