Rust Data LabData lab · live
Live readings Servers11,635 Players30,176 Populated2,756 Fresh wipes · 3h70 Sampled every 5 min

Element card · group Modded · atomic number 7,122, its rank

Ruka_RustServer

Online 162.43.9.12:28015 checked 10m ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 50 0% full Room to join
7-day average0peak 2
Rank · atomic number#7,122top 32%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
00.250.50.75106:0015:0000:0008:0017:0003:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
05010015020006:0015:0000:0008:0017:0003:00

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 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k21 Sep29 Sep6 Oct14 Oct21 Oct29 Oct

Top 32% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap11.2 daysbetween real wipes
wipe-day peak8players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 2 OctMon 21 Sep
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 14, 27 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 09:05 UTC26d ago 14 – running 0
Mon 21 Sep, 05:11 UTC38d ago 2 held half 11.2 days 0

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
  1. 1 Sh ShockRust | Bl… 41
    ShockRust | Blue | NoLimit no group limit · 152 on average 41/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 123
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 123/ 100
  3. 3 Re RETRO RUST #1 … 38
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average 38/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 15
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 15/ 700
  5. 5 Ru RustSpain.com … 2
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 2/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 4
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 4/ 1,000

Quick answers

from the figures on this page

Settings and map

What map is in play on Ruka_RustServer?

A procedural map of size 5,000 with seed 981907749 runs on Ruka_RustServer, generated by the game. You can view it on RustMaps from this page, since matching size and seed produce the same map.

How is Ruka_RustServer configured, and what rules apply?

No gather rate appears in the name of Ruka_RustServer. Groups top out at 8 players, the default for the game. Play runs as survival, raiding, building and gathering: the standard game. You can fight other players and raid them. The server browser lists it under Modded, where plugins or settings change the game. Plugins in use: Oxide. Anti-cheat is on: Valve's VAC.

About the server

What region hosts Ruka_RustServer?

No region is published by Ruka_RustServer. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 162.43.9.12:28015 is the address it uses.

Which Rust version is Ruka_RustServer on?

Rust network protocol 2635 and build 168909 on Linux is what Ruka_RustServer uses. The protocol must match for you to join; Steam will update your game.

Does Ruka_RustServer stay up, and how reliable is its uptime?

Ruka_RustServer is live as of now. About 5 days 20 hours ago is when it last restarted, based on its uptime. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. The first sighting by Rust Data Lab was on 21 September 2026.

Does Ruka_RustServer hold a steady performance?

The last 48 hours show an average of 75 server fps and a minimum of 48. Buildings, deployables and everything else in the world added up to as many as 156,212 entities. Up to 6,022 MB of memory was used. Players feel lag when fps is low and the entity count climbs.

Wipe days

When does Ruka_RustServer wipe, and how often?

Ruka_RustServer's wipe history on record is too thin yet to tell its rhythm. The next monthly force wipe, which wipes all Rust servers, is scheduled for Thursday 5 November at 19:00 UTC. 26 days 20 hours ago the current world was made.

What does a typical wipe day on Ruka_RustServer involve?

At their busiest, recent wipes averaged 8 players. The latest wipe's peak fell 27 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

Where it appears

Which meanings sit behind the tags on Ruka_RustServer?

gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 is the slot count; ts8 (Group limit): 8 per team, the default the game ships with; v2635 (Protocol): Protocol 2635 is required; join only if your game matches it; cs168909 (Build): It runs build 168909; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): The region field is left blank; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it lists under Modded: that is the tag list Ruka_RustServer publishes, and the game's server browser reads it. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Which Rust Data Lab filters and lists does Ruka_RustServer appear in?

You will find Ruka_RustServer on the following Rust Data Lab lists: Modded Rust servers, measured. You can find it on the server list by applying these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does Ruka_RustServer hold among Rust servers?

Ruka_RustServer sits at #7,122 for seven-day player hours, placing it in the top 32% of ranked servers.

How full is Ruka_RustServer right now?

Of 50 slots, 0 are taken on Ruka_RustServer right now. A seven-day sample gives 0 players on average and 2 at the top. Peak time in the past 48 hours: 16:00 UTC, when the average was 1 players.

Connection

How can you connect to Ruka_RustServer?

You can connect by pressing F1 in Rust and entering client.connect 162.43.9.12:28015, or by pressing Launch Rust here, which starts the game through Steam and joins for you.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp50
Max players 50 is the slot count.
ts8
Group limit 8 per team, the default the game ships with.
v2635
Protocol Protocol 2635 is required; join only if your game matches it.
cs168909
Build It runs build 168909.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code The region field is left blank.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it lists under Modded.

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.