On the class lists: F (27), with population over 48 hours and no performance mark.
Players now0/ 2000% full
7-day average1peak 1
Rank#8,141top 37%
Last wipe2d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 1 of 200 on average. Plenty of space to grow.
Standingrank on player hours
63/ 100
C
Working its way up from the back of the class: #8,141 on player hours.
Uptimehours on the list, last 48
17/ 100
F
Attendance needs work: on the list only 8 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 250 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in performance (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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 37% 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 peak1players, last three wipes
The first 48 hours of its last wipes
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
Mon 26 Oct, 23:28 UTC2d ago
1
–
running
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
No region is published for Rust 170 Devblog. Rust Server Score takes the server's word for its location and does not trace the hardware. 45.157.118.153:28015 is the address to use.
Is Rust 170 Devblog up, and how steady is its uptime?
You can join now: Rust 170 Devblog is online. The uptime it reports puts the last restart at about 2 hours ago. For the last 2 full days, it was up 10 of 48 hours, or 21% of the time. On 26 October 2026, Rust Server Score saw it for the first time.
Is Rust 170 Devblog smooth to play on?
The average over the last 48 hours was 253 server fps, and it never went below 226. At its peak, it held 36,444 entities, including buildings, deployables and all else in the world. Memory use reached up to 539 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is Rust 170 Devblog running?
The server Rust 170 Devblog is on Rust network protocol 2001 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Rust 170 Devblog wipe, and how often?
There are too few wipes on record for Rust 170 Devblog to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 2 days 2 hours.
What should you expect from wipe day on Rust 170 Devblog?
The average peak on its recent wipes was 1 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does Rust 170 Devblog sit among Rust servers?
Over the last seven days, Rust 170 Devblog has #8,141 for player hours, in the top 37% of all ranked servers.
Is Rust 170 Devblog a busy server?
Right now, 0 players are on Rust 170 Devblog, which has 200 slots. Averaging 1 players over seven days, it peaked at 1. The highest average in the last 48 hours came at 03:00 UTC, with 1 players.
Tags
What do Rust 170 Devblog's tags stand for?
The game's browser takes its cue from the tags Rust 170 Devblog has set: mp200 (Max players): The server holds 200 slots; v2001 (Protocol): Join only if your game runs protocol 2001; oxide (Oxide): Oxide (uMod) provides the plugin framework here; modded (Modded): The game is changed by plugins or settings; you will find it under Modded; h6de18208 (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one; stok (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one. 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 Rust 170 Devblog?
These Rust Server Score lists count Rust 170 Devblog among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Last wipe: In the last 3 days.
Rules and settings
How is Rust 170 Devblog set up, and what rules does it keep?
The name of Rust 170 Devblog gives no gather rate. No group limit is published. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The server runs Valve's anti-cheat, VAC.
Which map is in play on Rust 170 Devblog?
The game generates the procedural map on Rust 170 Devblog at size 4,000 with seed 170. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to Rust 170 Devblog?
To connect, start Rust, press F1, and type client.connect 45.157.118.153:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asoxide,modded,mp200,v2001,h6de18208,stok
Game
mp200
Max playersThe server holds 200 slots.
v2001
ProtocolJoin only if your game runs protocol 2001.
Mods and access
oxide
OxideOxide (uMod) provides the plugin framework here.
modded
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Other
h6de18208
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
stok
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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 performance (A+); population is the one to work on (F).