Online 37.18.21.171:35000 checked 9m ago
OMSK | WipeBlock |K i T | 16 - 30
Connect
srv = rust.server("37.18.21.171:35002")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 19% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 19h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 19h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 14d 23h | Thu 12 Nov, 23:20 UTC | wipe |
| 2 | 35d 19h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 3 | 42d 23h | Thu 10 Dec, 23:20 UTC | wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 23:20 UTC13d ago | 7 | NaN | running | 0 |
| 1 | Thu 1 Oct, 21:05 UTC FW27d ago | 8 | halved by day 6 | 14.1 days | 0 |
| 2 | 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.
display(srv.map, srv.info())Map
4500 · seed 882159982
- map
- Procedural Map
- size
- 4500
- seed
- 882159982
Server
srv.info()- address
- 37.18.21.171:35000
- region
- –
- max players
- 100
- group limit
- 10 max
- wipe schedule
- biweekly
- last wipe
- 15 Oct 2026, 23:20 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Friendly Seattle: No KOS | Chill | Noob Friendly | NA · groups of 8+ · biweekly · 40 on average | 48/100 |
| 1 | ［JP］初心者PVPサーバー｜RaidTime・ Events | EA · groups of 10+ · biweekly · 17 on average | 2/100 |
| 2 | СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10 | EU · groups of 50+ · biweekly · 9 on average | 3/200 |
| 3 | RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ | EU · groups of 8+ · biweekly · 8 on average | 5/200 |
| 4 | Rust Empires II - Roleplay/RP friendly, Cities, PVE, No KOS out | groups of 8+ · biweekly · 5 on average | 9/50 |
| 5 | [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 | EA · no group limit · biweekly · 4 on average | 0/20 |
Quick answers
From the figures on this page.
Population data
How does OMSK | WipeBlock |K i T | 16 - 30 compare in the rankings?
Over the last seven days OMSK | WipeBlock |K i T | 16 - 30 sits at #4,160 on player hours, in the top 19% of ranked servers.
How full does OMSK | WipeBlock |K i T | 16 - 30 run?
The sample now reads 0 players for OMSK | WipeBlock |K i T | 16 - 30, out of 100 slots. Over the last seven days it averaged 0 players and peaked at 4. The 48-hour sample puts the busiest hour at 19:00 UTC, averaging 3 players.
Server data
What does performance look like on OMSK | WipeBlock |K i T | 16 - 30?
The 48-hour average is 149 server fps, with a low of 101. Entity numbers reached 125,424, and that includes buildings, deployables and the rest. Memory peaked at 3,920 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is OMSK | WipeBlock |K i T | 16 - 30 on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by OMSK | WipeBlock |K i T | 16 - 30. The protocol has to match before you can join, and Steam does the updating.
How reliable is OMSK | WipeBlock |K i T | 16 - 30, and is it online now?
The current sample puts OMSK | WipeBlock |K i T | 16 - 30 online. The uptime it reports puts the last restart about 56 minutes ago. Over the last 7 full days the hours up number 166 of 168, 99%. Rust Data logged it first on 13 September 2026.
In which location is OMSK | WipeBlock |K i T | 16 - 30 hosted?
There is no region published for OMSK | WipeBlock |K i T | 16 - 30. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 37.18.21.171:35000.
Map and rules
What rules and settings are recorded for OMSK | WipeBlock |K i T | 16 - 30?
No gather rate appears in the name: OMSK | WipeBlock |K i T | 16 - 30. The cap on a group is 10 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on OMSK | WipeBlock |K i T | 16 - 30?
The game generates the map on OMSK | WipeBlock |K i T | 16 - 30: procedural, size 4,500, seed 882159982. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
On what schedule does OMSK | WipeBlock |K i T | 16 - 30 wipe?
Wipes on OMSK | WipeBlock |K i T | 16 - 30 run every 4 weeks on Thursday at 23:20 UTC. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 13 days ago. The tags list a two-weekly wipe cycle.
What is wipe day on OMSK | WipeBlock |K i T | 16 - 30 like?
The average peak over recent wipes is 10 players. 43 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 6.5.
Lists and tags
Which lists on Rust Data hold OMSK | WipeBlock |K i T | 16 - 30, and which filters?
The Rust Data lists that OMSK | WipeBlock |K i T | 16 - 30 fits are: Modded Rust servers. Under these filters on the server list, it is listed: 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 should you read the server tags on OMSK | WipeBlock |K i T | 16 - 30?
These tags are published by OMSK | WipeBlock |K i T | 16 - 30 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts10 (Group limit): Team size tops out at 10; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): The cycle is fourteen days; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to OMSK | WipeBlock |K i T | 16 - 30?
Enter client.connect 37.18.21.171:35000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://discord.com/invite/khp73Xxq.