OMSK | WipeBlock |K i T | 16 - 30
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 8m ago · 37.18.21.171:35000
Abstract
We describe the public Rust server OMSK | WipeBlock |K i T | 16 - 30, reached at 37.18.21.171:35000. At the last check it held 0 of 100 places, against a seven-day mean of 0 and a peak of 41. It ranks #4,158 of all servers, the top 19%. It last wiped 13d ago on a published biweekly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
Keywordsbiweekly wipes modded oxide
1Summary statistics
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.
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).
4Rank
The server stands in the top 19% 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.
5Wipes
5.1Schedule: fixed weekdays
The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 14h. The force wipe (high confidence).
| Measure | Value | Note |
|---|---|---|
| Usual gap | 28 days | between real wipes |
| On rhythm | 100% | of its recent wipes |
| Wipe-day peak | 10 | players, last three wipes |
| Crowd held | 0% | else halves by day 6.5 |
| When (UTC) | In | Kind |
|---|---|---|
| Thu 5 Nov, 19:00 | 7d 14h | force wipefw |
| Thu 12 Nov, 23:20 | 14d 18h | its own schedule |
| Thu 3 Dec, 19:00 | 35d 14h | force wipefw |
| Thu 10 Dec, 23:20 | 42d 18h | its own schedule |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Thu 15 Oct, 23:2013d ago | 7 | – | running | 0 |
| Thu 1 Oct, 21:05fw27d ago | 8 | halved by day 6 | 14.1 d | 0 |
| Thu 17 Sep, 23:1541d ago | 15 | halved by day 7 | 13.9 d | 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. 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
| 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 |
| Map | Procedural Map |
| Size | 4500 |
| Seed | 882159982 |
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 Rust wipe forecast [3].
| Server | Players |
|---|---|
| Friendly Seattle: No KOS | Chill | Noob FriendlyNA · groups of 8+ · biweekly · 41 on average | 43/100 |
| [JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 17 on average | 2/100 |
| СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10EU · groups of 50+ · biweekly · 9 on average | 0/200 |
| RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮEU · groups of 8+ · biweekly · 8 on average | 2/200 |
| Rust Empires II - Roleplay/RP friendly, Cities, PVE, No KOS outgroups of 8+ · biweekly · 5 on average | 11/50 |
| [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29EA · no group limit · biweekly · 4 on average | 0/20 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1Does OMSK | WipeBlock |K i T | 16 - 30 perform well?
The server fps averaged 147 over the last 48 hours, never dropping below 101. The highest number of entities it carried was 125,403, comprising buildings, deployables and all other objects. Memory use peaked at 3,920 MB. Players experience lag when fps is low and the entity count is rising.
A.2What is the location of OMSK | WipeBlock |K i T | 16 - 30?
There is no region published for OMSK | WipeBlock |K i T | 16 - 30. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 37.18.21.171:35000.
A.3What is the reliability of OMSK | WipeBlock |K i T | 16 - 30, and is it online?
OMSK | WipeBlock |K i T | 16 - 30 is currently online. It last restarted around 5 hours ago, according to its reported uptime. Of the 168 hours in the last 7 full days, 165 were served, an availability of 98%. The first record of it by Rust Statistics dates to 13 September 2026.
A.4What is the Rust version for OMSK | WipeBlock |K i T | 16 - 30?
OMSK | WipeBlock |K i T | 16 - 30 is running Rust network protocol 2635 and build 168909 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.
Wipe timing
A.5What schedule does OMSK | WipeBlock |K i T | 16 - 30 follow for wipes?
The wipe rhythm of 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; this server's next wipe is then. The current world has been running for 13 days 5 hours. Wipes every two weeks are published in the tags.
A.6What happens on OMSK | WipeBlock |K i T | 16 - 30 when wipe day arrives?
Across its recent wipes, the average peak population was 10 players. The crowd reached its maximum 43 hours after the latest wipe. For 0% of recent wipes, the population did not fall below half the peak before the next wipe. If not, the population dropped below half by day 6.5.
Population
A.7How does OMSK | WipeBlock |K i T | 16 - 30 compare with other Rust servers in the rankings?
The seven-day player-hours ranking puts OMSK | WipeBlock |K i T | 16 - 30 at #4,158, within the top 19% of ranked servers.
A.8At what level does OMSK | WipeBlock |K i T | 16 - 30 operate in terms of players?
The current population of OMSK | WipeBlock |K i T | 16 - 30 is 0, drawn from 100 slots. Averaged over the last seven days: 0 players; the same period peaks at 4. Of the last 48 hours, the peak hour falls at 19:00 UTC, with an average of 3 players.
Tags, lists
A.9What do the tags associated with OMSK | WipeBlock |K i T | 16 - 30 signify?
Tags from OMSK | WipeBlock |K i T | 16 - 30, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp100 (Max players): It offers 100 slots; ts10 (Group limit): A team holds no more than 10; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^b (Biweekly): Every two weeks the server wipes; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game. The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.10Where can OMSK | WipeBlock |K i T | 16 - 30 be found among the Rust Statistics lists and filters?
These Rust Statistics lists include OMSK | WipeBlock |K i T | 16 - 30: Modded Rust servers. It appears under the following filters 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.
Rules, settings, map
A.11What are the settings and rules that govern OMSK | WipeBlock |K i T | 16 - 30?
No gather rate appears in the name of OMSK | WipeBlock |K i T | 16 - 30. 10 players is the cap on a group. The mode is survival, which means gather, build and raid: the standard game. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Oxide. The server has VAC on, Valve's anti-cheat.
A.12What is the map for OMSK | WipeBlock |K i T | 16 - 30?
Size 4,500 and seed 882159982 define the procedural, game-generated map on OMSK | WipeBlock |K i T | 16 - 30. Equal size and seed yield an identical map, which this page offers to view on RustMaps.
Connection
A.13What steps are required to join OMSK | WipeBlock |K i T | 16 - 30?
Enter client.connect 37.18.21.171:35000 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you. You can find its website at https://discord.com/invite/khp73Xxq.
Appendix BServer tags
What each of the server's tags means. Published as mp100,ptrak,$r?,v2635,^b,gmrust,cs168909,ts10,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. This is survival as standard Rust plays. |
mp100 | Max players. It offers 100 slots. |
ts10 | Group limit. A team holds no more than 10. |
v2635 | Protocol. The game protocol is 2635; your client must match it to join. |
cs168909 | Build. This server runs game build 168909. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. A region code has not been set. |
| Wipe schedule | |
^b | Biweekly. Every two weeks the server wipes. |
| Mods and access | |
^o | Oxide. Oxide (uMod), a plugin framework, runs on this server. |
^z | Modded. Modded listing: plugins or settings modify the game. |
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.
Appendix CAbout this server, in its own words
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.