Working its way up from the back of the class: #14,305 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
34/ 100
F
Lost ground: down 4,540 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
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
Top 61% 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
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 [RU] TOKIO RUST | X5 | NOLIM | 25.09 sit?
No region tag appears for [RU] TOKIO RUST | X5 | NOLIM | 25.09, but the name suggests Europe. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 89.248.236.148:27101 is the address to use.
How reliable is [RU] TOKIO RUST | X5 | NOLIM | 25.09, and is it up?
You cannot join now: [RU] TOKIO RUST | X5 | NOLIM | 25.09 is offline, last seen 33 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 26 September 2026, Rust Server Score saw it for the first time.
Which Rust version is [RU] TOKIO RUST | X5 | NOLIM | 25.09 running?
The server [RU] TOKIO RUST | X5 | NOLIM | 25.09 is on Rust network protocol 2633 and build 165217 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does [RU] TOKIO RUST | X5 | NOLIM | 25.09 reset?
The record holds too few of [RU] TOKIO RUST | X5 | NOLIM | 25.09'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 33 days 11 hours.
Player count
Where does [RU] TOKIO RUST | X5 | NOLIM | 25.09 sit among Rust servers?
In the top 61% of all ranked servers, [RU] TOKIO RUST | X5 | NOLIM | 25.09 sits at #14,305 for player hours over the last seven days.
Is [RU] TOKIO RUST | X5 | NOLIM | 25.09 a busy server?
It has been 33 days 6 hours since [RU] TOKIO RUST | X5 | NOLIM | 25.09 was last seen, and it is offline right now.
Tags
How should you read the tags on [RU] TOKIO RUST | X5 | NOLIM | 25.09?
The game's browser takes its cue from the tags [RU] TOKIO RUST | X5 | NOLIM | 25.09 has set: gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): Its slot count is 40; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): This runs on build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; jp0 (Custom tag): The owner or a plugin created this tag, so it is not standard Rust. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show [RU] TOKIO RUST | X5 | NOLIM | 25.09?
These Rust Server Score lists count [RU] TOKIO RUST | X5 | NOLIM | 25.09 among them: 5x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 5x.
Server rules
Which rules does [RU] TOKIO RUST | X5 | NOLIM | 25.09 enforce, and what are its settings?
The name of [RU] TOKIO RUST | X5 | NOLIM | 25.09 points to a 5x gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
[RU] TOKIO RUST | X5 | NOLIM | 25.09 runs which map?
A procedural map, generated by the game, is what [RU] TOKIO RUST | X5 | NOLIM | 25.09 runs.
Getting in
How should you connect to [RU] TOKIO RUST | X5 | NOLIM | 25.09?
To connect, start Rust, press F1, and type client.connect 89.248.236.148:27101. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,jp0,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersIts slot count is 40.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
jp0
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
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. Even marks across the subjects, from F to F.