Working its way up from the back of the class: #14,332 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
51/ 100
D
Moving up: up 250 places this week.
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.
No daily history yet.
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 65% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
In what location does My Rust Devblog 133 Server on Version 1051.72 sit?
My Rust Devblog 133 Server on Version 1051.72 leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 117.20.69.122:28015 is the address to use.
Is My Rust Devblog 133 Server on Version 1051.72 up, and how steady is its uptime?
You cannot join now: My Rust Devblog 133 Server on Version 1051.72 is offline, last seen 19 days 3 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 10 October 2026.
What Rust version is My Rust Devblog 133 Server on Version 1051.72 on?
Rust network protocol 1806 on Windows is what My Rust Devblog 133 Server on Version 1051.72 runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does My Rust Devblog 133 Server on Version 1051.72 reset?
The record holds too few of My Rust Devblog 133 Server on Version 1051.72's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server.
Player count
Where does My Rust Devblog 133 Server on Version 1051.72 sit among Rust servers?
In the top 65% of all ranked servers, My Rust Devblog 133 Server on Version 1051.72 sits at #14,332 for player hours over the last seven days.
How many players does My Rust Devblog 133 Server on Version 1051.72 usually have?
The last sighting of My Rust Devblog 133 Server on Version 1051.72 was 19 days 3 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on My Rust Devblog 133 Server on Version 1051.72?
mp1 (Max players): The server holds 1 slots; v1806 (Protocol): Join only if your game runs protocol 1806; oxide (Oxide): Plugin framework: Oxide (uMod); modded (Modded): The game is changed by plugins or settings; you will find it under Modded; h815a96ff (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner are the tags My Rust Devblog 133 Server on Version 1051.72 publishes, and the game's server browser reads them. 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.
Which Rust Server Score filters and lists feature My Rust Devblog 133 Server on Version 1051.72?
These Rust Server Score lists count My Rust Devblog 133 Server on Version 1051.72 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded.
Server rules
What settings and rules apply on My Rust Devblog 133 Server on Version 1051.72?
The name of My Rust Devblog 133 Server on Version 1051.72 gives no gather rate. It publishes no limit on group size. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. You are not covered by VAC, Valve's anti-cheat.
My Rust Devblog 133 Server on Version 1051.72 runs which map?
The game generates a procedural map for My Rust Devblog 133 Server on Version 1051.72.
Connecting
How do you get onto My Rust Devblog 133 Server on Version 1051.72?
To connect, start Rust, press F1, and type client.connect 117.20.69.122:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asoxide,modded,mp1,v1806,h815a96ff
Game
mp1
Max playersThe server holds 1 slots.
v1806
ProtocolJoin only if your game runs protocol 1806.
Mods and access
oxide
OxidePlugin framework: Oxide (uMod).
modded
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Other
h815a96ff
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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).