Working its way up from the back of the class: #15,846 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
50/ 100
D
Holding steady: up 145 places this week.
A term to build on.
Strongest in momentum (D); standing 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
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
Where in the world is Mon Serveur Local AutoUpdate?
No region is published for Mon Serveur Local AutoUpdate. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 185.147.212.228:28015.
Is Mon Serveur Local AutoUpdate up, and how steady is its uptime?
At this moment, Mon Serveur Local AutoUpdate is offline; the last time it was seen was 18 days 10 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.
What Rust version is Mon Serveur Local AutoUpdate on?
Rust network protocol 2632 and build 160556 on Windows is what Mon Serveur Local AutoUpdate runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Mon Serveur Local AutoUpdate reset?
The record holds too few of Mon Serveur Local AutoUpdate'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. 18 days 10 hours have passed since this world was made.
Player numbers
Where does Mon Serveur Local AutoUpdate place in the wider field of Rust servers?
Over the last seven days, Mon Serveur Local AutoUpdate has #15,846 for player hours, in the top 72% of all ranked servers.
What does the population on Mon Serveur Local AutoUpdate look like?
Mon Serveur Local AutoUpdate is offline at the moment; the last time it was seen was 18 days 10 hours ago.
Tags and filters
What do Mon Serveur Local AutoUpdate's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp2 (Max players): 2 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2632 (Protocol): Join only if your game runs protocol 2632; cs160556 (Build): This runs on build 160556; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Mon Serveur Local AutoUpdate publishes, and the game's server browser reads them. 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 Rust Server Score filters and lists feature Mon Serveur Local AutoUpdate?
These Rust Server Score lists count Mon Serveur Local AutoUpdate among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Mon Serveur Local AutoUpdate?
Nothing in the name of Mon Serveur Local AutoUpdate states a 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. VAC, Valve's anti-cheat, is enabled.
Mon Serveur Local AutoUpdate runs which map?
The game generates a procedural map for Mon Serveur Local AutoUpdate.
Getting in
How do you get onto Mon Serveur Local AutoUpdate?
To connect, start Rust, press F1, and type client.connect 185.147.212.228:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2632,gmrust,cs160556,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp2
Max players2 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2632
ProtocolJoin only if your game runs protocol 2632.
cs160556
BuildThis runs on build 160556.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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. Strongest in momentum (D); standing is the one to work on (F).