Working its way up from the back of the class: #15,922 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: down 38 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.
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 17 Sep. 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
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 peak4players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 18 Sep, 12:27 UTC40d ago
4
–
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
In what location does MomoServer Re:START seazon2 sit?
MomoServer Re:START seazon2 leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 85.131.248.106:28015 is the address to use.
How dependable is MomoServer Re:START seazon2, and is it online at the moment?
At this moment, MomoServer Re:START seazon2 is offline; the last time it was seen was 20 days 13 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is MomoServer Re:START seazon2 running?
The server MomoServer Re:START seazon2 is on Rust network protocol 2633 and build 162929 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does MomoServer Re:START seazon2 wipe, and how often?
The record holds too few of MomoServer Re:START seazon2'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. 40 days 1 hours have passed since this world was made.
What should you expect from wipe day on MomoServer Re:START seazon2?
Recent wipes have peaked at 4 players on average. Peak numbers came 3 hours into the latest wipe.
Population
Where does MomoServer Re:START seazon2 place in the wider field of Rust servers?
Over the last seven days, MomoServer Re:START seazon2 has #15,922 for player hours, in the top 72% of all ranked servers.
How many players does MomoServer Re:START seazon2 usually have?
It has been 20 days 13 hours since MomoServer Re:START seazon2 was last seen, and it is offline right now.
Lists and filters
What do MomoServer Re:START seazon2's tags stand for?
The game's browser takes its cue from the tags MomoServer Re:START seazon2 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs162929 (Build): This runs on build 162929; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature MomoServer Re:START seazon2?
Rust Server Score lists that include MomoServer Re:START seazon2: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is MomoServer Re:START seazon2 set up, and what rules does it keep?
You will find no gather rate in the name of MomoServer Re:START seazon2. The default of 8 players applies as the group cap. pve is the mode here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on MomoServer Re:START seazon2?
The game generates the procedural map on MomoServer Re:START seazon2 at size 2,700 with seed 19686. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
Connecting
How should you connect to MomoServer Re:START seazon2?
To connect, start Rust, press F1, and type client.connect 85.131.248.106:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/fVQCdAVAQY.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,^p,gmrust,cs162929,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs162929
BuildThis runs on build 162929.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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).