Working its way up from the back of the class: #15,835 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
37/ 100
F
Slipped a little: down 4,017 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.
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 72% 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
You'll find no region listed by Mon Serveur Local. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 77.195.88.41:28015.
Is Mon Serveur Local up, and how steady is its uptime?
At this moment, Mon Serveur Local is offline; the last time it was seen was 19 days 7 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 8 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Mon Serveur Local running?
Rust network protocol 2634 and build 167231 on Windows is what Mon Serveur Local runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Mon Serveur Local wipe, and how often?
The record holds too few of Mon Serveur Local's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 19 days 14 hours.
Player count
What position does Mon Serveur Local hold in the rankings?
In the top 72% of all ranked servers, Mon Serveur Local sits at #15,835 for player hours over the last seven days.
How many players does Mon Serveur Local usually have?
Mon Serveur Local is offline at the moment; the last time it was seen was 19 days 7 hours ago.
Lists and filters
What do Mon Serveur Local's tags stand for?
The game's browser takes its cue from the tags Mon Serveur Local has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167231 (Build): The game build is 167231; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here. 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 Mon Serveur Local appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Mon Serveur Local among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does Mon Serveur Local enforce, and what are its settings?
Nothing in the name of Mon Serveur Local states a 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. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Mon Serveur Local?
A procedural map, generated by the game, is what Mon Serveur Local runs.
Connecting
What is the way to join Mon Serveur Local?
To connect, start Rust, press F1, and type client.connect 77.195.88.41:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167231,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167231
BuildThe game build is 167231.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set 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. Even marks across the subjects, from F to F.