Working its way up from the back of the class: #13,651 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
22/ 100
F
Lost ground: down 7,618 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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 57% 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 peak3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 25 Sep, 05:11 UTC34d ago
3
–
running
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 Local Rust Server leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 58.104.146.249:28015.
How dependable is My Local Rust Server, and is it online at the moment?
At this moment, My Local Rust Server is offline; the last time it was seen was 28 days 23 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is My Local Rust Server running?
You will find My Local Rust Server on Rust network protocol 2633 and build 163207, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does My Local Rust Server wipe its map?
There are too few wipes on record for My Local Rust Server to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 34 days 16 hours.
What happens on My Local Rust Server when wipe day arrives?
The average peak on its recent wipes was 3 players. Peak numbers came 0 hours into the latest wipe.
Population
What position does My Local Rust Server hold in the rankings?
In the top 57% of all ranked servers, My Local Rust Server sits at #13,651 for player hours over the last seven days.
How many players does My Local Rust Server usually have?
My Local Rust Server is offline at the moment; the last time it was seen was 28 days 23 hours ago.
Tags and filters
What do My Local Rust Server's tags stand for?
The game's browser takes its cue from the tags My Local Rust Server has set: gmhardcore (Game mode): The ruleset is hardcore, the harsher one; mp3 (Max players): 3 slots are available; ts0 (Group limit): Teams are disabled; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163207 (Build): Build number: 163207; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under 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 My Local Rust Server?
Rust Server Score lists that include My Local Rust Server: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o.
Map and rules
What settings and rules apply on My Local Rust Server?
The name of My Local Rust Server gives no gather rate. It publishes no limit on group size. It runs hardcore, Facepunch's most punishing mode. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on My Local Rust Server?
A procedural map, generated by the game, is what My Local Rust Server runs.
Getting in
How do you get onto My Local Rust Server?
Enter client.connect 58.104.146.249: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 asmp3,ptrak,$r?,v2633,gmhardcore,cs163207,ts0,^o^z
Game
gmhardcore
Game modeThe ruleset is hardcore, the harsher one.
mp3
Max players3 slots are available.
ts0
Group limitTeams are disabled.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163207
BuildBuild number: 163207.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is 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. Strongest in standing (F); momentum is the one to work on (F).