Station XX-15341 · recording
oborotty Server
Online 118.156.125.160:28015 checked 8m ago
- Players now
- 0/ 500
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,341
- top 69%
- Last wipe
- 89d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 500 slots
- Motion · 24 h
- M0.0■steady+0 players
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 69% 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.
- usual gap
- 3.4 daysbetween real wipes
- wipe-day peak
- 2players, last three wipes
- crowd held
- 0%else halves by day 2
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 5 Oct, 18:19 UTC23d ago | M0.0▲rising | 1 | – | running | 0 | |
| Fri 2 Oct, 07:53 UTC27d ago | M0.5▲rising | 3 | halved by day 2 | 3.4 days | 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 pageRules and settings
Which map is running on oborotty Server?
The procedural map on oborotty Server is size 4,500 with seed 1337, 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 oborotty Server?
The name of oborotty Server gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on oborotty Server?
0 of the 500 slots on oborotty Server are filled right now. Averaged across the last seven days, the population was 0 players.
How does oborotty Server rank against other Rust servers?
On player hours for the past week, oborotty Server sits at #15,341, which puts it inside the top 69% of every ranked server.
Server details
How reliably does oborotty Server stay online?
Right now, you can reach oborotty Server. Going by the uptime figure it reports, it restarted about 2 days 2 hours ago. Of the 168 hours in the last 7 full days, it was up for 82, or 49% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Does oborotty Server hold a steady tick rate?
Its average server fps over the last 48 hours was 88, and it never dropped below 32. Buildings, deployables and all the rest of the world's entities brought it to a high of 141,981. It reached a ceiling of 3,985 MB of memory. Low fps together with a growing entity count is what players experience as lag.
Where in the world is oborotty Server hosted?
A region is not published by oborotty Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 118.156.125.160:28015.
Which Rust version is oborotty Server running?
On Windows, oborotty Server runs Rust network protocol 2634 and build 166586. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on oborotty Server?
2 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. It fell under half by day 2 in the wipes where it didn't hold.
How often does oborotty Server wipe, and on which days?
The rhythm of oborotty Server cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 89 days 8 hours.
Server tags
What do the server tags on oborotty Server mean?
The game's server browser reads the tags oborotty Server publishes: gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166586 (Build): It runs game build 166586; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does oborotty Server appear?
These Rust Server Trends lists include oborotty Server: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto oborotty Server?
Enter client.connect 118.156.125.160: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.