Station XX-7994 · recording
Rust 170 Devblog
Online 45.157.118.153:28015 checked 10m ago
- Players now
- 0/ 200
- 0% full
- Motion · 24 h
- M0.0▼falling
- −1 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #7,994
- top 36%
- Last wipe
- 2d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 200 slots
- Motion · 24 h
- M0.0▼falling−1 players
- Sharpest hour
- +0into Wed 23:00 UTC
- Peak · 48 h
- 1most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 36% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 1players, 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 26 Oct, 23:28 UTC2d ago | M0.0▲rising | 1 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Rust 170 Devblog?
The procedural map on Rust 170 Devblog is size 4,000 with seed 170, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Rust 170 Devblog?
You will find no gather rate in the name of Rust 170 Devblog. No group limit is published. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on Rust 170 Devblog right now?
At this moment, Rust 170 Devblog records 0 players across 200 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 1. The last 48 hours show their highest activity at 16:00 UTC, averaging 1 players.
How does Rust 170 Devblog rank against other Rust servers?
The last seven days of player hours place Rust 170 Devblog at #7,994, in the top 36% of all ranked servers.
Server facts
How reliably does Rust 170 Devblog stay online?
Right now, you can reach Rust 170 Devblog. Its reported uptime points to a restart about 5 hours ago. 10 of 48 hours in the last 2 full days were up time, 21% of the total. On 26 October 2026 it was recorded for the first time by Rust Server Trends.
How well does Rust 170 Devblog perform under load?
Its average server fps over the last 48 hours was 258, and it never dropped below 226. At its highest, it carried 36,565 entities: buildings, deployables and the world's other contents. It reached a ceiling of 539 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Where in the world is Rust 170 Devblog hosted?
No region is published by Rust 170 Devblog. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 45.157.118.153:28015.
What build of Rust does Rust 170 Devblog use?
Rust network protocol 2001 on Windows is what Rust 170 Devblog runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Rust 170 Devblog?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
How often does Rust 170 Devblog wipe, and on which days?
On record so far are too few of Rust 170 Devblog's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 2 days 12 hours.
Tags
What do the server tags on Rust 170 Devblog mean?
These are the tags Rust 170 Devblog publishes for the browser to read: mp200 (Max players): Slots: 200; v2001 (Protocol): Game protocol 2001: to join, your game must match this version; oxide (Oxide): A plugin framework, Oxide (uMod), runs here; modded (Modded): Plugins or settings alter the game, so it's listed under Modded; h6de18208 (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin; stok (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Rust 170 Devblog appear?
The Rust Server Trends lists that take in Rust 170 Devblog are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Last wipe: In the last 3 days.
Connecting
What steps get you onto Rust 170 Devblog?
Enter client.connect 45.157.118.153:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.