Station XX-4167 · recording
OMSK | WipeBlock |K i T | 16 - 30
Online 37.18.21.171:35000 checked 10m ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 4
- Rank
- #4,167
- top 19%
- Last wipe
- 13d ago
- biweekly schedule
- Next wipe
- 7d 16h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −2into Tue 23:00 UTC
- Peak · 48 h
- 3most 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 19% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 7d 16h. The force wipe · high confidence
- usual gap
- 28 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 10players, last three wipes
- crowd held
- 0%else halves by day 6.5
Coming wipes
- 7d 16hThu 5 Nov, 19:00 UTCFW
- 14d 20hThu 12 Nov, 23:20 UTC
- 35d 16hThu 3 Dec, 19:00 UTCFW
- 42d 20hThu 10 Dec, 23:20 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 7, 43 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 23:20 UTC13d ago | M0.8▲rising | 7 | – | running | 0 | |
| Thu 1 Oct, 21:05 UTC FW27d ago | M0.9▲rising | 8 | halved by day 6 | 14.1 days | 0 | |
| Thu 17 Sep, 23:15 UTC41d ago | M1.1▲rising | 15 | halved by day 7 | 13.9 days | 1 |
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 pageRules and settings
Which map is running on OMSK | WipeBlock |K i T | 16 - 30?
Generated by the game, the map on OMSK | WipeBlock |K i T | 16 - 30 is procedural, size 4,500 with seed 882159982. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on OMSK | WipeBlock |K i T | 16 - 30?
No gather rate appears in the name of OMSK | WipeBlock |K i T | 16 - 30. The group limit is 10 players. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on OMSK | WipeBlock |K i T | 16 - 30?
At this moment, OMSK | WipeBlock |K i T | 16 - 30 records 0 players across 100 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 4. The last 48 hours show their highest activity at 19:00 UTC, averaging 3 players.
How does OMSK | WipeBlock |K i T | 16 - 30 rank against other Rust servers?
Over the last seven days, OMSK | WipeBlock |K i T | 16 - 30 recorded enough player hours to reach #4,167 worldwide, placing it in the top 19% of all ranked servers.
Server facts
How reliably does OMSK | WipeBlock |K i T | 16 - 30 stay online?
As recorded now, OMSK | WipeBlock |K i T | 16 - 30 is running. Going by the uptime figure it reports, it restarted about 3 hours ago. 165 of 168 hours in the last 7 full days were up time, 98% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
Does OMSK | WipeBlock |K i T | 16 - 30 hold a steady tick rate?
Its average server fps over the last 48 hours was 147, and it never dropped below 101. At its highest, it carried 125,424 entities: buildings, deployables and the world's other contents. Memory use peaked at 3,920 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Where in the world is OMSK | WipeBlock |K i T | 16 - 30 hosted?
Nothing about a region comes from OMSK | WipeBlock |K i T | 16 - 30. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 37.18.21.171:35000.
What build of Rust does OMSK | WipeBlock |K i T | 16 - 30 use?
Rust network protocol 2635 and build 168909 on Windows is what OMSK | WipeBlock |K i T | 16 - 30 runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on OMSK | WipeBlock |K i T | 16 - 30?
On average, the busiest point of its recent wipes drew 10 players. 43 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 6.5 it fell below half in the wipes where it didn't hold.
On what timetable does OMSK | WipeBlock |K i T | 16 - 30 run its wipes?
The wipe rhythm at OMSK | WipeBlock |K i T | 16 - 30 is every 4 weeks on Thursday at 23:20 UTC. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. It has run its current world for 13 days 3 hours. In its tags it sets out a wipe schedule of every two weeks.
Server tags
What do the server tags on OMSK | WipeBlock |K i T | 16 - 30 mean?
These are the tags OMSK | WipeBlock |K i T | 16 - 30 publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): The server has 100 slots; ts10 (Group limit): Teams are capped at 10 players; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does OMSK | WipeBlock |K i T | 16 - 30 appear?
These Rust Server Trends lists include OMSK | WipeBlock |K i T | 16 - 30: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
How to join
How do you connect to OMSK | WipeBlock |K i T | 16 - 30?
Enter client.connect 37.18.21.171:35000 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://discord.com/invite/khp73Xxq.
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.