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
Where in the world is LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
You'll find no region listed by LOCAL RUST X10 | Kits | RaidBlock | WipeBlock. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 145.255.140.99:28015.
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 41 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
On what Rust version does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock sit?
You will find LOCAL RUST X10 | Kits | RaidBlock | WipeBlock on Rust network protocol 2633 and build 163794, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock wipe, and how often?
LOCAL RUST X10 | Kits | RaidBlock | WipeBlock has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 42 days 8 hours.
Player numbers
Where does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock place in the wider field of Rust servers?
In the top – of all ranked servers, LOCAL RUST X10 | Kits | RaidBlock | WipeBlock sits at #15,491 for player hours over the last seven days.
How many players does LOCAL RUST X10 | Kits | RaidBlock | WipeBlock usually have?
The last sighting of LOCAL RUST X10 | Kits | RaidBlock | WipeBlock was 41 days 6 hours ago, and it is offline right now.
Tags 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): Rust survival, played by the standard rules; mp20 (Max players): The server holds 20 slots; ts4 (Group limit): A team can hold 4 players at most; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): This runs on build 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^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 lists and filters on Rust Server Score show 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. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Quad; Gather rate: 10x.
Server rules
How is LOCAL RUST X10 | Kits | RaidBlock | WipeBlock set up, and what rules does it keep?
LOCAL RUST X10 | Kits | RaidBlock | WipeBlock sets gather at 10x, as its name suggests. The cap on group size is 4 players (quad). survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
The game generates a procedural map for LOCAL RUST X10 | Kits | RaidBlock | WipeBlock.
Connecting
What is the way to join LOCAL RUST X10 | Kits | RaidBlock | WipeBlock?
To connect, start Rust, press F1, and type client.connect 145.255.140.99:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
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 playersThe server holds 20 slots.
ts4
Group limitA team can hold 4 players at most.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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.
Not enough figures yet to write a report. Check back after a few days on the list.