Rust PopulationField survey · Rust servers
Observing 78,222 players 11,801 servers 3,772 with someone on 109 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 8,814habitat unknownfirst seen 26 Oct 2026

Rust 170 Devblog

Offline 45.157.118.153:28015 checked 4h ago

Measurements

Players now
1/ 200
= 1 player
0% full
7-day average
1
peak 1
Rank
#8,814
top 40%
Last wipe
1d ago
no schedule published
Next wipe
–
too few wipes seen yet
Obs. 1 · sightings

Players

AveragePeakWipe
00.250.50.75121:0023:0000:0002:0003:0016:00Wiped Mon 26 Oct, 23:28 UTCWIPE

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

Server fpsWipe
010020030040021:0023:0000:0002:0003:0016:00Wiped Mon 26 Oct, 23:28 UTCWIPE

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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Oct27 Oct28 Oct

Top 40% of all ranked servers. Ranked on player hours over the last seven days.

Obs. 4 · the wipe cycle

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.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 23:28 UTC1d ago – – 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.

Field questions

Quick answers

from the figures on this page

Player counts

How does Rust 170 Devblog rank against other Rust servers?

Over the past week it ranks #8,814 for player hours, which puts Rust 170 Devblog in the top 40% of all ranked servers.

How busy is Rust 170 Devblog?

At this count Rust 170 Devblog is offline, with its last sighting 4 hours ago. We counted an average of 1 players in the past week, with 1 at the busiest. Look at the last 48 hours and 00:00 UTC stands out: it averaged 1 players.

Lists and tags

What do the server tags on Rust 170 Devblog mean?

These are the tags Rust 170 Devblog publishes, as read by the game's server browser: mp200 (Max players): You can join up to 200 slots; v2001 (Protocol): To join, your game must match protocol 2001; h2bb0056b (Custom tag): The owner or a plugin applied this tag, which is not standard Rust; stok (Custom tag): The owner or a plugin applied this tag, which is not standard Rust. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include Rust 170 Devblog?

On Rust Population, Rust 170 Devblog is filed under these lists: Community servers, field-listed. Filter the server list by Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 3 days and it will show up.

Wipe schedule

What is the wipe schedule on Rust 170 Devblog?

The record holds too few of Rust 170 Devblog's wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 45 hours ago.

Settings

Which map does Rust 170 Devblog run?

The map on Rust 170 Devblog is procedural, made by the game at size 4,000 from seed 170. Size and seed together fix the map, so you can view it on RustMaps from this page.

What are the rules and settings on Rust 170 Devblog?

The name tells you nothing about gather rates: Rust 170 Devblog states none. You will find no published group limit here. You get survival here, the usual game, where you gather, build and raid. Combat between players, raids included, is permitted. A community server, it appears in the Community section of the browser. The anti-cheat VAC from Valve is enabled.

Server details

Which version of Rust does Rust 170 Devblog run?

On Windows, Rust 170 Devblog runs Rust network protocol 2001. The protocol must match for you to join, and Steam updates it for you.

Does Rust 170 Devblog run smoothly?

It ran at 258 server fps on average over the last 48 hours, and never went below 252. Up to 36,302 entities were present, counting buildings, deployables and everything else. Memory use peaked at 564 MB. What players experience as lag comes from low fps and a rising entity count.

Is Rust 170 Devblog online, and how reliable is it?

Currently offline, Rust 170 Devblog was last seen 4 hours ago. The uptime it reports suggests a restart roughly 38 minutes ago. In the last 1 full day it was found up for 4 of 24 hours, 17% of the time. On 26 October 2026, Rust Population saw it for the first time.

Where is Rust 170 Devblog located?

No region is published by Rust 170 Devblog. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. 45.157.118.153:28015 is where it lives.

How to join

How do I join Rust 170 Devblog?

Open the console with F1 in Rust and enter client.connect 45.157.118.153:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.

Key to its markings

Server tags

what each one means

Published as mp200,v2001,h2bb0056b,stok

Game

mp200
Max players You can join up to 200 slots.
v2001
Protocol To join, your game must match protocol 2001.

Other

h2bb0056b
Custom tag The owner or a plugin applied this tag, which is not standard Rust.
stok
Custom tag The owner or a plugin applied this tag, which is not standard Rust.

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.