Working its way up from the back of the class: #15,226 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
46/ 100
D
Slipped a little: down 1,103 places this week. Nothing a good wipe can't fix.
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.
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··WFW··
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap0.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Fri 2 OctThu 1 OctWed 30 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 19 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 16:37 UTC25d ago
1
–
running
0
Thu 1 Oct, 18:31 UTCFW26d ago
1
–
0.9 days
0
Wed 30 Sep, 19:49 UTC27d ago
1
–
0.9 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
MyLovelyServer leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 86.0.232.59:28015.
Is MyLovelyServer up, and how steady is its uptime?
You cannot join now: MyLovelyServer is offline, last seen 13 days 18 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 28 September 2026.
Which Rust version is MyLovelyServer running?
The server MyLovelyServer is on Rust network protocol 2634 and build 166652 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does MyLovelyServer reset?
There is no next wipe to predict on MyLovelyServer, as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 25 days 18 hours.
What should you expect from wipe day on MyLovelyServer?
Across its recent wipes, the busiest moments averaged 1 players. 19 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does MyLovelyServer place in the wider field of Rust servers?
Over the last seven days, MyLovelyServer has #15,226 for player hours, in the top 70% of all ranked servers.
Is MyLovelyServer a busy server?
It has been 13 days 18 hours since MyLovelyServer was last seen, and it is offline right now.
Tags
What is meant by the tags on MyLovelyServer?
The game's browser takes its cue from the tags MyLovelyServer has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as 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.
Which lists and filters on Rust Server Score show MyLovelyServer?
These Rust Server Score lists count MyLovelyServer 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.
Map and rules
What settings and rules apply on MyLovelyServer?
You will find no gather rate in the name of MyLovelyServer. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: 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. The server runs Valve's anti-cheat, VAC.
MyLovelyServer runs which map?
MyLovelyServer runs a procedural map, which the game generates.
How to join
How do you get onto MyLovelyServer?
Enter client.connect 86.0.232.59: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,cs166652,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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).