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
In what location does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock sit?
LOCAL RUST X10 | Kits | RaidBlock | WipeBlock leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 46.38.11.161:28015 is the address to use.
How reliable is LOCAL RUST X10 | Kits | RaidBlock | WipeBlock, and is it up?
The server is down: LOCAL RUST X10 | Kits | RaidBlock | WipeBlock is offline now, with the last sighting 42 days 11 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 16 September 2026, Rust Server Score saw it for the first time.
Which Rust version is LOCAL RUST X10 | Kits | RaidBlock | WipeBlock running?
You will find LOCAL RUST X10 | Kits | RaidBlock | WipeBlock on Rust network protocol 2633 and build 163794, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock wipe its map?
The record holds too few of LOCAL RUST X10 | Kits | RaidBlock | WipeBlock's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 42 days 11 hours.
Player numbers
Where does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock place in the wider field of Rust servers?
Over the last seven days, LOCAL RUST X10 | Kits | RaidBlock | WipeBlock has #15,203 for player hours, in the top – of all ranked servers.
What does the population on LOCAL RUST X10 | Kits | RaidBlock | WipeBlock look like?
It has been 42 days 11 hours since LOCAL RUST X10 | Kits | RaidBlock | WipeBlock was last seen, and it is offline right now.
Lists and filters
What do LOCAL RUST X10 | Kits | RaidBlock | WipeBlock's tags stand for?
You'll see LOCAL RUST X10 | Kits | RaidBlock | WipeBlock tagged with gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): Its slot count is 20; ts8 (Group limit): A team can hold 8 at most, which is the game default; 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): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
Rust Server Score lists that include LOCAL RUST X10 | Kits | RaidBlock | WipeBlock: 10x Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 10x.
Rules and settings
How is LOCAL RUST X10 | Kits | RaidBlock | WipeBlock set up, and what rules does it keep?
Going by its name, LOCAL RUST X10 | Kits | RaidBlock | WipeBlock runs 10x gather. 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. 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 LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
A procedural map, generated by the game, is what LOCAL RUST X10 | Kits | RaidBlock | WipeBlock runs.
Getting in
How should you connect to LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
Enter client.connect 46.38.11.161: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,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max playersIts slot count is 20.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 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
OxidePlugin framework: Oxide (uMod).
^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.
Not enough figures yet to write a report. Check back after a few days on the list.