Working its way up from the back of the class: #13,130 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
35/ 100
F
Slipped a little: down 3,995 places this week. Nothing a good wipe can't fix.
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.
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 59% of all ranked servers. Ranked on player hours over the last seven days.
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 peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in, with 1 in the queue.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 19:41 UTC25d ago
1+1 queue
–
running
0
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
NA · groups of 8+ · 3x · biweekly · 105 on average
42 / 100
Quick answers
from the figures on this page
Server facts
Which region is [TR] M.A.K 3X - SOLO/DUO [TP/KIT] based in?
You'll find no region listed by [TR] M.A.K 3X - SOLO/DUO [TP/KIT]. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 163.5.53.252:30120.
How reliable is [TR] M.A.K 3X - SOLO/DUO [TP/KIT], and is it up?
The server is down: [TR] M.A.K 3X - SOLO/DUO [TP/KIT] is offline now, with the last sighting 17 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 3 October 2026, Rust Server Score saw it for the first time.
On what Rust version does [TR] M.A.K 3X - SOLO/DUO [TP/KIT] sit?
The server [TR] M.A.K 3X - SOLO/DUO [TP/KIT] is on Rust network protocol 2634 and build 166652 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does [TR] M.A.K 3X - SOLO/DUO [TP/KIT] wipe its map?
[TR] M.A.K 3X - SOLO/DUO [TP/KIT] has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 25 days 8 hours have passed since this world was made.
What should you expect from wipe day on [TR] M.A.K 3X - SOLO/DUO [TP/KIT]?
Recent wipes have peaked at 1 players on average. With 1 players queued, the latest wipe's crowd peaked 0 hours after it started.
Population
Where does [TR] M.A.K 3X - SOLO/DUO [TP/KIT] sit among Rust servers?
In the top 59% of all ranked servers, [TR] M.A.K 3X - SOLO/DUO [TP/KIT] sits at #13,130 for player hours over the last seven days.
What does the population on [TR] M.A.K 3X - SOLO/DUO [TP/KIT] look like?
It has been 17 days 12 hours since [TR] M.A.K 3X - SOLO/DUO [TP/KIT] was last seen, and it is offline right now.
Lists and filters
What do [TR] M.A.K 3X - SOLO/DUO [TP/KIT]'s tags stand for?
The game's browser takes its cue from the tags [TR] M.A.K 3X - SOLO/DUO [TP/KIT] has set: gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): Its slot count is 2; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $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. 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.
Where does [TR] M.A.K 3X - SOLO/DUO [TP/KIT] appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [TR] M.A.K 3X - SOLO/DUO [TP/KIT]: 3x 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: 5 or more; Gather rate: 3x.
Map and rules
Which rules does [TR] M.A.K 3X - SOLO/DUO [TP/KIT] enforce, and what are its settings?
The name of [TR] M.A.K 3X - SOLO/DUO [TP/KIT] points to a 3x gather rate. With no change from the game default, groups take up to 8 players. 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. You are covered by VAC, Valve's anti-cheat.
[TR] M.A.K 3X - SOLO/DUO [TP/KIT] runs which map?
The game generates the procedural map on [TR] M.A.K 3X - SOLO/DUO [TP/KIT] at size 3,700 with seed 1356766082. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto [TR] M.A.K 3X - SOLO/DUO [TP/KIT]?
To connect, start Rust, press F1, and type client.connect 163.5.53.252:30120. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp2
Max playersIts slot count is 2.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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.
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.