Working its way up from the back of the class: #15,321 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
33/ 100
F
Lost ground: down 5,288 places this week. A strong wipe could turn it round.
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.
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 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W·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.
usual gap1.3 daysbetween real wipes
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Sat 17 OctThu 15 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 03:58 UTC11d ago
2
–
running
0
Thu 15 Oct, 20:37 UTC12d ago
2
–
1.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
You'll find no region listed by MorningStar | PvE. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 177.112.90.80:28015.
How dependable is MorningStar | PvE, and is it online at the moment?
At this moment, MorningStar | PvE is offline; the last time it was seen was 10 days 9 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 15 October 2026, Rust Server Score saw it for the first time.
What Rust version is MorningStar | PvE on?
The server MorningStar | PvE is on Rust network protocol 2634 and build 167781 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does MorningStar | PvE wipe, and how often?
There are too few wipes on record for MorningStar | PvE 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. The world it runs now was created 11 days 11 hours.
What happens on MorningStar | PvE when wipe day arrives?
Recent wipes have peaked at 2 players on average. The crowd on the latest wipe was largest 1 hours after it began.
Player numbers
Where does MorningStar | PvE sit among Rust servers?
In the top 70% of all ranked servers, MorningStar | PvE sits at #15,321 for player hours over the last seven days.
Is MorningStar | PvE a busy server?
MorningStar | PvE is offline at the moment; the last time it was seen was 10 days 9 hours ago.
Tags and filters
How should you read the tags on MorningStar | PvE?
The game's browser takes its cue from the tags MorningStar | PvE has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts10 (Group limit): A team can hold 10 players at most; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does MorningStar | PvE appear in the Rust Server Score lists and filters?
These Rust Server Score lists count MorningStar | PvE among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
Which rules does MorningStar | PvE enforce, and what are its settings?
The name of MorningStar | PvE gives no gather rate. A group here can reach 10 players. 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 as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
MorningStar | PvE runs which map?
MorningStar | PvE runs a game-generated procedural map at size 6,000, seed 1337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to MorningStar | PvE?
Enter client.connect 177.112.90.80:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts10,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts10
Group limitA team can hold 10 players at most.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under 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. Even marks across the subjects, from F to F.