Rust Server Analytics 32,508 players11,637 servers
All servers
Drill-through Server detail

Rust 170 Devblog

Online 45.157.118.153:28015 checked 7m ago

Drill-through
FilterServeris Rust 170 Devblog
Attributes
modded
Last refreshed
Players now 1/ 200
7-day average 1 peak 1
Rank #8,143 top 37%
Last wipe 2d ago no schedule published
Next wipe – too few wipes seen yet
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
00.250.50.75115:0020:0022:0023:0001:0003:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
010020030040015:0020:0022:0023:0001:0003:00

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
15k10k15k20k26 Oct27 Oct28 Oct29 Oct

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

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

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
ShockRust | Blue | NoLimit no group limit · 153 on average 35 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 123 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average 59 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 13 / 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 2 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 3 / 1000

Quick answers

from the figures on this page

Wipe cycle

The wipe schedule for Rust 170 Devblog: what is it?

Too few wipes on record for Rust 170 Devblog to show its rhythm. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. 2 days 5 hours ago the current world was made.

Wipe day on Rust 170 Devblog: what should you expect?

Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe the crowd peaked.

Server details

What is the hosting location of Rust 170 Devblog?

No region is published by Rust 170 Devblog. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. The address of the server is 45.157.118.153:28015.

What Rust build does Rust 170 Devblog run?

The platform is Windows, with Rust network protocol 2001 running on Rust 170 Devblog. Your game must match the protocol to join, and Steam applies that update.

Is Rust 170 Devblog up, and how steady is its uptime?

As of the latest refresh, Rust 170 Devblog is online. The uptime it reports puts the last restart at about 5 hours ago. 21% uptime over the last 2 full days, equal to 10 of 48 hours. 26 October 2026 is when Rust Server Analytics first recorded it.

What performance does Rust 170 Devblog show?

Over 48 hours the average held at 257 server fps, and the minimum was 226. Buildings, deployables and all other world objects brought the entity total to 36,565. Peak memory was 539 MB. A climbing entity count and low fps are the lag players perceive.

Lists and tags

What do Rust 170 Devblog's tags stand for?

The game's server browser reads the tags Rust 170 Devblog publishes: mp200 (Max players): 200 slots in total; v2001 (Protocol): To join, your game version must match protocol 2001; oxide (Oxide): It runs Oxide (uMod) for plugins; modded (Modded): The Modded section, because plugins or settings modify play; h6de18208 (Custom tag): Outside the standard tag set, added by the owner or a plugin; stok (Custom tag): Outside the standard tag set, added by the owner or a plugin. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

On Rust Server Analytics, which lists and filters feature Rust 170 Devblog?

The following Rust Server Analytics lists count Rust 170 Devblog among their servers: Modded Rust servers: live data. It appears on the server list under the following filters: Type: Modded; Last wipe: In the last 3 days.

Population

What position does Rust 170 Devblog hold in the server rankings?

On player hours over seven days, Rust 170 Devblog ranks #8,143, within the top 37% of ranked servers.

What is the population of Rust 170 Devblog?

Of 200 slots, 1 are filled on Rust 170 Devblog at this refresh. Averaging 1 players across seven days, the server reached a peak of 1. Across the last 48 hours, 16:00 UTC shows the highest average: 1 players.

Map and rules

What settings and rules does Rust 170 Devblog use?

No gather rate is given in the name of Rust 170 Devblog. Group limit: not published. survival is the game mode, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. In the server browser it sits under Modded, where plugins or settings alter the game. The server runs with VAC, Valve's anti-cheat, enabled.

The map on Rust 170 Devblog: which one is it?

A procedural map of size 4,000 with seed 170, generated by the game, runs on Rust 170 Devblog. The map is reproducible from its size and seed and can be seen on RustMaps from here.

Connection

How do you connect to Rust 170 Devblog?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 45.157.118.153:28015.

Server tags

what each one means

Published as oxide,modded,mp200,v2001,h6de18208,stok

Game

mp200
Max players 200 slots in total.
v2001
Protocol To join, your game version must match protocol 2001.

Mods and access

oxide
Oxide It runs Oxide (uMod) for plugins.
modded
Modded The Modded section, because plugins or settings modify play.

Other

h6de18208
Custom tag Outside the standard tag set, added by the owner or a plugin.
stok
Custom tag Outside the standard tag set, added by the owner or a plugin.

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.