On the class lists: B− (70), with population over 48 hours and no performance mark.
Players now2/ 1020% full
7-day average0peak 2
Rank#8,995top 40%
Last wipe4d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
4/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
60/ 100
C
Working its way up from the back of the class: #8,995 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 136 places this week.
A term to build on.
Strongest in wipe hold (A+); population 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 40% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
8 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W·W·
······W
·W·W···
··WW·W·
····
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 gap2 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Sat 24 OctThu 22 OctWed 21 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 23:21 UTC4d ago
2
–
running
0
Thu 22 Oct, 12:36 UTC7d ago
1
✓ held half
2.4 days
1
Wed 21 Oct, 11:56 UTC8d ago
1
–
1 days
1
Thu 15 Oct, 13:55 UTC14d ago
1
–
5.9 days
1
Tue 13 Oct, 12:59 UTC16d ago
1
✓ held half
2 days
1
Sun 11 Oct, 18:00 UTC17d ago
1
–
1.8 days
0
Sat 3 Oct, 21:54 UTC25d ago
1
✓ held half
7.8 days
0
Sat 3 Oct, 15:16 UTC26d ago
1
–
0.3 days
1
Thu 1 Oct, 14:50 UTC28d ago
1
–
2 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
Which region is My Local Rust Server [78.147.38.91:28015] based in?
No region is published for My Local Rust Server [78.147.38.91:28015]. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 78.147.38.91:28015 is the address to use.
How dependable is My Local Rust Server [78.147.38.91:28015], and is it online at the moment?
The server is down: My Local Rust Server [78.147.38.91:28015] is offline now, with the last sighting 4 days 16 hours ago. It was up 16 of 168 hours over the last 7 full days, which is 10% of the time. On 1 October 2026, Rust Server Score saw it for the first time.
What Rust version is My Local Rust Server [78.147.38.91:28015] on?
The server My Local Rust Server [78.147.38.91:28015] is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does My Local Rust Server [78.147.38.91:28015] reset?
There is no next wipe to predict on My Local Rust Server [78.147.38.91:28015], as it wipes at irregular times. 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 4 days 18 hours.
What happens on My Local Rust Server [78.147.38.91:28015] when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 100% of its recent wipes.
Player count
What position does My Local Rust Server [78.147.38.91:28015] hold in the rankings?
In the top 40% of all ranked servers, My Local Rust Server [78.147.38.91:28015] sits at #8,995 for player hours over the last seven days.
What does the population on My Local Rust Server [78.147.38.91:28015] look like?
It has been 4 days 16 hours since My Local Rust Server [78.147.38.91:28015] was last seen, and it is offline right now. Averaging 0 players over seven days, it peaked at 2.
Tags and filters
How should you read the tags on My Local Rust Server [78.147.38.91:28015]?
The game's browser takes its cue from the tags My Local Rust Server [78.147.38.91:28015] has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does My Local Rust Server [78.147.38.91:28015] appear in the Rust Server Score lists and filters?
Rust Server Score lists that include My Local Rust Server [78.147.38.91:28015]: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
Server rules
Which rules does My Local Rust Server [78.147.38.91:28015] enforce, and what are its settings?
The name of My Local Rust Server [78.147.38.91:28015] gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on My Local Rust Server [78.147.38.91:28015]?
The game generates a procedural map for My Local Rust Server [78.147.38.91:28015].
Getting in
What is the way to join My Local Rust Server [78.147.38.91:28015]?
Enter client.connect 78.147.38.91: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?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max players10 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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 wipe hold (A+); population is the one to work on (F).