A quiet classroom so far: 0 of 80 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,341 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
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
49/ 100
D
Slipped a little: down 216 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population is the one to work on (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
Every five minutes, from the Steam server list.
AveragePeak
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.
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
11 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
···W···
WW·W···
···WW··
···W···
·W·W···
···W···
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Thu 22 OctThu 15 OctTue 13 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 09:06 UTC6d ago
0
–
running
0
Thu 15 Oct, 09:06 UTC13d ago
0
–
7 days
0
Tue 13 Oct, 01:57 UTC16d ago
0
–
2.3 days
0
Thu 8 Oct, 09:06 UTC20d ago
0
–
4.7 days
0
Fri 2 Oct, 09:07 UTC26d ago
0
–
6 days
0
Thu 1 Oct, 09:06 UTC27d ago
0
–
1 days
0
Thu 24 Sep, 19:20 UTC34d ago
0
–
6.6 days
0
Thu 24 Sep, 09:05 UTC34d ago
0
–
0.4 days
0
Tue 22 Sep, 19:12 UTC36d ago
0
–
1.6 days
0
Mon 21 Sep, 23:51 UTC37d ago
0
–
0.8 days
0
Thu 17 Sep, 09:05 UTC41d ago
0
–
4.6 days
0
Sat 12 Sep, 02:27 UTC47d ago
0
–
5.3 days
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
31 / 100
Quick answers
from the figures on this page
Server details
Which region is Mi Server Rust x3 Hardcore based in?
No region is published for Mi Server Rust x3 Hardcore. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 200.115.209.238:28015.
How dependable is Mi Server Rust x3 Hardcore, and is it online at the moment?
Right now, Mi Server Rust x3 Hardcore is online. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is Mi Server Rust x3 Hardcore on?
The server Mi Server Rust x3 Hardcore is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Mi Server Rust x3 Hardcore wipe its map?
No next wipe can be predicted for Mi Server Rust x3 Hardcore, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 6 days 21 hours.
What happens on Mi Server Rust x3 Hardcore when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
What position does Mi Server Rust x3 Hardcore hold in the rankings?
In the top 69% of all ranked servers, Mi Server Rust x3 Hardcore sits at #15,341 for player hours over the last seven days.
What does the population on Mi Server Rust x3 Hardcore look like?
Right now, 0 players are on Mi Server Rust x3 Hardcore, which has 80 slots. A seven-day average of 0 players applies here.
Tags and filters
What do Mi Server Rust x3 Hardcore's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp80 (Max players): Its slot count is 80; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags Mi Server Rust x3 Hardcore publishes, and the game's server browser reads them. 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 Mi Server Rust x3 Hardcore?
These Rust Server Score lists count Mi Server Rust x3 Hardcore among them: 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 Carbon ^y; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 3x.
Rules and settings
How is Mi Server Rust x3 Hardcore set up, and what rules does it keep?
Mi Server Rust x3 Hardcore sets gather at 3x, as its name suggests. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Mi Server Rust x3 Hardcore uses?
A procedural map, generated by the game, is what Mi Server Rust x3 Hardcore runs.
Getting in
What is the way to join Mi Server Rust x3 Hardcore?
To connect, start Rust, press F1, and type client.connect 200.115.209.238:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp80,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp80
Max playersIts slot count is 80.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework here.
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. Strongest in uptime (A+); population is the one to work on (F).