OMSK | WipeBlock |K i T | 16 - 30
Online 37.18.21.171:35000 checked 8m ago
Vital stats
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
Top 19% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 18h. The force wipe · high confidence
Coming wipes
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 23:20 UTC13d ago | 7 | – | running | 0 |
| Thu 1 Oct, 21:05 UTC FW27d ago | 8 | halved by day 6 | 14.1 days | 0 |
| Thu 17 Sep, 23:15 UTC41d ago | 15 | halved by day 7 | 13.9 days | 1 |
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.
Quick answers
From the figures on this page.
Lists and tags
Which Rust Pop Watch lists and filters include OMSK | WipeBlock |K i T | 16 - 30?
These are the Rust Pop Watch lists that include OMSK | WipeBlock |K i T | 16 - 30: Modded Rust servers, 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.
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: gmrust (Game mode): This one runs standard Rust survival, as it comes; mp100 (Max players): It has 100 slots; ts10 (Group limit): No team can exceed 10 players; v2635 (Protocol): The game protocol is 2635, so your client has to match it to join; cs168909 (Build): Game build: 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): Region code left blank; ^b (Biweekly): The server wipes every fortnight; ^o (Oxide): A plugin framework called Oxide (uMod) is running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue and world age are in the tags too, displayed at the top of this page.
Population
How does OMSK | WipeBlock |K i T | 16 - 30 rank against other Rust servers?
Player hours over the last week rank OMSK | WipeBlock |K i T | 16 - 30 at #4,164, within the top 19% of ranked servers.
How many players are on OMSK | WipeBlock |K i T | 16 - 30 right now?
OMSK | WipeBlock |K i T | 16 - 30 is holding 0 players, with 100 slots in total. Peak for the week was 4, against an average of 0 players. Look at 19:00 UTC: that was the busiest point of the last 48 hours, at 3 players on average.
Server facts
Is OMSK | WipeBlock |K i T | 16 - 30 online, and how reliable is it?
OMSK | WipeBlock |K i T | 16 - 30 is live at the moment. About 1 hours ago is when it last restarted, judging by its uptime. The last 7 full days saw uptime of 85%, with 142 out of 168 hours online. It came to Rust Pop Watch's attention on 13 September 2026.
Does OMSK | WipeBlock |K i T | 16 - 30 run smoothly?
Its server fps over the last 48 hours averaged 148, with 101 as the lowest. At its peak it held 125,424 entities: buildings, deployables and all the rest. Up to 3,920 MB of memory was used. Lag, for players, is low fps and an entity count that keeps climbing.
Where is OMSK | WipeBlock |K i T | 16 - 30 located?
No region is published by OMSK | WipeBlock |K i T | 16 - 30. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. You'll find it at 37.18.21.171:35000.
Which Rust version is OMSK | WipeBlock |K i T | 16 - 30 on?
On Windows, OMSK | WipeBlock |K i T | 16 - 30 runs Rust network protocol 2635 and build 168909. Joining requires your game to match the protocol, which Steam updates for you.
Wipe times
What happens on OMSK | WipeBlock |K i T | 16 - 30 when wipe day comes around?
Recent wipes averaged a peak of 10 players at their busiest. 43 hours after the latest wipe, the crowd hit its peak. Its recent wipes kept the crowd above half the peak until the next one 0% of the time. In the wipes that didn't hold, the crowd sank below half by day 6.5.
What is the wipe schedule on OMSK | WipeBlock |K i T | 16 - 30?
Wipes on OMSK | WipeBlock |K i T | 16 - 30 follow a every 4 weeks on Thursday at 23:20 UTC pattern. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Its current world has been live for 13 days 1 hours. Its tags set out a wipe schedule of one wipe every two weeks.
Map and rules
Which map does OMSK | WipeBlock |K i T | 16 - 30 run?
Generated by the game with seed 882159982, the map on OMSK | WipeBlock |K i T | 16 - 30 is procedural and 4,500 in size. Look at it on RustMaps from this page: the same size and seed always make the same map.
What are the rules and settings on OMSK | WipeBlock |K i T | 16 - 30?
Nothing in the name tells you the gather rate on OMSK | WipeBlock |K i T | 16 - 30. Teams can reach 10 players. It runs survival, gather, build and raid, as standard. Raids and PvP are both on the table. It is a Modded listing: plugins or settings change how the game plays. Oxide plugins power it. Anti-cheat is on: VAC, Valve's system.
Getting in
How do I join OMSK | WipeBlock |K i T | 16 - 30?
The console method: start Rust, press F1, and type client.connect 37.18.21.171:35000. Launch Rust on this page is another way, opening Rust via Steam and connecting. For more, see https://discord.com/invite/khp73Xxq.