Rust StatisticsWorking papers on every public Rust server · 32,367 players now

Rust 170 Devblog

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 6m ago · 45.157.118.153:28015

Abstract

We describe the public Rust server Rust 170 Devblog, reached at 45.157.118.153:28015. At the last check it held 1 of 200 places, against a seven-day mean of 1 and a peak of 11. It ranks #8,143 of all servers, the top 37%. It last wiped 2d ago.

Keywordsmodded

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/2000% full
In the queue0no queue
Seven-day mean1peak 1, 48 h peak 1
Rank2#8,143top 37%
Last wipe2d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
00.250.50.75115:0020:0022:0023:0001:0003:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
010020030040015:0020:0022:0023:0001:0003:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 37% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k26 Oct27 Oct28 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak1players, last three wipes
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 26 Oct, 23:282d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 5: The map: Procedural Map, size 4000, seed 170. Open on RustMaps.
Table 4: The server's published settings.
Address45.157.118.153:28015
Region–
Max players200
Group limitnot published
Wipe schedule–
Last wipe26 Oct 2026, 23:28 UTC
Hostname–
First seen26 Oct 2026
MapProcedural Map
Size4000
Seed170

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 153 on average33/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average122/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average53/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average13/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average3/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of Rust 170 Devblog smooth?

Its average server fps over the last 48 hours was 257, with a minimum of 226. Its entity count reached a maximum of 36,565, including buildings, deployables and all other world objects. The peak memory usage was 539 MB. When fps is low and entity count climbs, players feel lag.

A.2What is the location of Rust 170 Devblog?

There is no region published for Rust 170 Devblog. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 45.157.118.153:28015 is its address.

A.3What is the reliability of Rust 170 Devblog, and is it online?

Rust 170 Devblog is currently online. The uptime it reports indicates a restart about 5 hours ago. The server was up 21% of the time over the last 2 full days, 10 of 48 hours. It was first observed on 26 October 2026 by Rust Statistics.

A.4What version of Rust is run on Rust 170 Devblog?

Rust network protocol 2001 is the version that Rust 170 Devblog runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.5What schedule does Rust 170 Devblog follow for wipes?

Too few wipes by Rust 170 Devblog have been recorded to determine the pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The world currently in use was created 2 days 5 hours ago.

A.6What happens on Rust 170 Devblog when wipe day arrives?

Recent wipes saw an average peak of 1 players. The peak on the latest wipe came 0 hours after it began.

Population

A.7What position does Rust 170 Devblog occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts Rust 170 Devblog at #8,143, within the top 37% of ranked servers.

A.8What is the population level of Rust 170 Devblog?

On Rust 170 Devblog, 1 of the 200 slots are occupied at present. Averaged over the last seven days: 1 players; the same period peaks at 1. Averaging 1 players, 16:00 UTC was the busiest hour of the past 48.

Tags and filters

A.9How should the tags on Rust 170 Devblog be interpreted?

The game's server browser reads mp200 (Max players): It offers 200 slots; v2001 (Protocol): The game protocol is 2001; your client must match it to join; oxide (Oxide): The plugin framework in use is Oxide (uMod); modded (Modded): Modded listing: plugins or settings modify the game; h6de18208 (Custom tag): This is not a standard Rust tag: it was set by the owner or by a plugin; stok (Custom tag): This is not a standard Rust tag: it was set by the owner or by a plugin, which Rust 170 Devblog publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can Rust 170 Devblog be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Rust 170 Devblog fits. You will find it on the server list filtered by: Type: Modded; Last wipe: In the last 3 days.

Rules, settings, map

A.11Under what rules and settings does Rust 170 Devblog operate?

No gather rate appears in the name of Rust 170 Devblog. A group limit is absent from what the server publishes. survival is the game mode here; gather, build and raid: the standard game. Players may raid and fight one another. Plugins or settings change the game; the browser files it under Modded. VAC is active: that is Valve's anti-cheat.

A.12What map is in use on Rust 170 Devblog?

Size 4,000 and seed 170 define the procedural, game-generated map on Rust 170 Devblog. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

How to join

A.13What is the process for joining Rust 170 Devblog?

Press F1 inside Rust to open the console and enter client.connect 45.157.118.153:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as oxide,modded,mp200,v2001,h6de18208,stok.

Table 6: The server's tags and their meanings.
TagMeaning
Game
mp200Max players. It offers 200 slots.
v2001Protocol. The game protocol is 2001; your client must match it to join.
Mods and access
oxideOxide. The plugin framework in use is Oxide (uMod).
moddedModded. Modded listing: plugins or settings modify the game.
Other
h6de18208Custom tag. This is not a standard Rust tag: it was set by the owner or by a plugin.
stokCustom tag. This is not a standard Rust tag: it was set by the owner or by 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.