Station XX-10368 · no signal
server_yarika
Offline 185.109.23.87:28015 checked 11h ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0▼falling
- −1 players on the day
- 7-day average
- 1
- peak 2
- Rank
- #10,368
- top 47%
- Last wipe
- 14h ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0▼falling−1 players
- Sharpest hour
- +1into Wed 10:00 UTC
- Peak · 48 h
- 2most players in any hour
- Events picked
- 1wipe on this record, in red
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 47% 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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 28 Oct, 09:06 UTC14h ago | – | – | – | – | running | 3 |
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 pageMap and rules
Which map is running on server_yarika?
server_yarika uses a procedural map, which the game generates.
Which settings and rules apply on server_yarika?
You will find no gather rate in the name of server_yarika. The group limit is 8 players, the game's default. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched off.
Player counts
What is the current population on server_yarika?
No players are recorded on server_yarika at this moment; it is offline, and the last sighting was 11 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 2. Averaged over the last 48 hours, the busiest hour was 10:00 UTC at 2 players.
How does server_yarika rank against other Rust servers?
The last seven days of player hours place server_yarika at #10,368, in the top 47% of all ranked servers.
Server details
How reliably does server_yarika stay online?
server_yarika is down at the moment; the last recorded contact was 11 hours ago. It was up 2% of the time across the last 7 full days: 4 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 11 October 2026.
Which region does server_yarika run from?
Nothing about a region comes from server_yarika. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 185.109.23.87:28015 is the address it uses.
What build of Rust does server_yarika use?
Rust network protocol 2635 and build 168909 on Windows is what server_yarika runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
On what timetable does server_yarika run its wipes?
On record so far are too few of server_yarika's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 14 hours is how long the current world has been running.
Tags
What do the server tags on server_yarika mean?
Tags published by server_yarika and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $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. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does server_yarika appear?
You will find server_yarika on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Join the server
How do you connect to server_yarika?
You can connect by pressing F1 in Rust and typing client.connect 185.109.23.87:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.