Working its way up from the back of the class: #13,640 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
47/ 100
D
Slipped a little: down 881 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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 62% 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
Mon Serveur Solo leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 92.184.109.228:28015.
How reliable is Mon Serveur Solo, and is it up?
The server is down: Mon Serveur Solo is offline now, with the last sighting 18 days 20 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 10 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Mon Serveur Solo sit?
The server Mon Serveur Solo is on Rust network protocol 2634 and build 167398 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Mon Serveur Solo wipe, and how often?
There are too few wipes on record for Mon Serveur Solo to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 18 days 21 hours.
Population
Where does Mon Serveur Solo sit among Rust servers?
Over the last seven days, Mon Serveur Solo has #13,640 for player hours, in the top 62% of all ranked servers.
How many players does Mon Serveur Solo usually have?
It has been 18 days 20 hours since Mon Serveur Solo was last seen, and it is offline right now.
Tags and filters
What do Mon Serveur Solo's tags stand for?
The game's browser takes its cue from the tags Mon Serveur Solo has set: gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167398 (Build): This runs on build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Mon Serveur Solo appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Mon Serveur Solo among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
What settings and rules apply on Mon Serveur Solo?
The name of Mon Serveur Solo gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Mon Serveur Solo uses?
A procedural map, generated by the game, is what Mon Serveur Solo runs.
Connecting
How do you get onto Mon Serveur Solo?
To connect, start Rust, press F1, and type client.connect 92.184.109.228:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs167398,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max players1 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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 D.