Working its way up from the back of the class: #14,094 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
32/ 100
F
Lost ground: down 5,060 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.
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 64% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
9 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
WWW···W
···WWW·
·······
·······
···
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.7 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Sat 10 OctFri 9 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 10 Oct, 19:27 UTC17d ago
1
–
running
1
Fri 9 Oct, 12:34 UTC18d ago
1
–
1.3 days
1
Thu 8 Oct, 16:42 UTC19d ago
1
–
0.8 days
1
Sun 4 Oct, 18:49 UTC23d ago
1
–
3.9 days
1
Sun 4 Oct, 09:38 UTC23d ago
1
–
0.4 days
1
Wed 30 Sep, 18:44 UTC27d ago
1
–
3.6 days
1
Wed 30 Sep, 10:11 UTC27d ago
1
–
0.4 days
1
Tue 29 Sep, 18:51 UTC28d ago
1
–
0.6 days
1
Tue 29 Sep, 10:10 UTC28d ago
1
–
0.4 days
1
Mon 28 Sep, 19:35 UTC29d ago
1
–
0.6 days
1
Sat 26 Sep, 14:11 UTC31d ago
1
–
2.2 days
0
Fri 25 Sep, 16:56 UTC32d ago
1
–
0.9 days
1
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
My Custom Rust Server leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 80.7.146.80:28015.
How reliable is My Custom Rust Server, and is it up?
At this moment, My Custom Rust Server is offline; the last time it was seen was 17 days 3 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 25 September 2026.
What Rust version is My Custom Rust Server on?
The server My Custom Rust Server is on Rust network protocol 2634 and build 167231 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does My Custom Rust Server reset?
My Custom Rust Server wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 17 days 4 hours.
What happens on My Custom Rust Server when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Player count
What position does My Custom Rust Server hold in the rankings?
Over the last seven days, My Custom Rust Server has #14,094 for player hours, in the top 64% of all ranked servers.
How many players does My Custom Rust Server usually have?
My Custom Rust Server is offline at the moment; the last time it was seen was 17 days 3 hours ago.
Tags
What do My Custom Rust Server's tags stand for?
The game's browser takes its cue from the tags My Custom Rust Server has set: gmrust (Game mode): Survival in the standard Rust style; 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; cs167231 (Build): Build number: 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does My Custom Rust Server appear in the Rust Server Score lists and filters?
These Rust Server Score lists count My Custom Rust Server among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is My Custom Rust Server set up, and what rules does it keep?
You will find no gather rate in the name of My Custom Rust Server. The default of 8 players applies as the group cap. It runs survival, 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. The server runs Valve's anti-cheat, VAC.
Connecting
How do you get onto My Custom Rust Server?
To connect, start Rust, press F1, and type client.connect 80.7.146.80:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167231,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
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.
cs167231
BuildBuild number: 167231.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^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.