Rust Data LabData lab · live
Live readings Servers11,612 Players36,584 Populated2,915 Fresh wipes · 3h70 Sampled every 5 min

Element card · group Community · atomic number 14,679, its rank

yaboss1

Offline 46.72.251.238:28015 checked 33d ago

Join the experiment
Atomic mass · players now 1/ 1 100% full Near capacity
7-day average0peak –
Rank · atomic number#14,679top 64%
Last wipe33d 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
No hourly history yet.

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
This server has not answered a direct query in the last 48 hours.

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k25 Sep26 Sep28 Sep29 Sep1 Oct2 Oct

Top 64% 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 25 Sep, 19:43 UTC33d ago 1 – running 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 Ru Rusty Moose |E… 209
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 531 on average 209/ 250
  2. 2 Ru Rustoria.co - … 200
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 200/ 225
  3. 3 Ru Rusty Moose |E… 17
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average 17/ 250
  4. 4 Ru Rustoria.co - … 18
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 280 on average 18/ 250
  5. 5 Ru Rustafied.com … 19
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average 19/ 100
  6. 6 Ru Rustoria.co - … 105
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 248 on average 105/ 200

Quick answers

from the figures on this page

Map and rules

What map is in play on yaboss1?

Generated by the game, the map on yaboss1 is procedural.

What settings and rules apply on yaboss1?

No gather rate appears in the name of yaboss1. Eight players per group is the limit, the game's default. survival is the game mode, raiding, building and gathering: the standard game. Fighting and raiding between players are allowed. You will find it under Community in the server browser. The VAC anti-cheat from Valve is enabled.

Server details

Which location is yaboss1 based in?

No region is published by yaboss1. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. 46.72.251.238:28015 is the address it uses.

On what Rust version does yaboss1 operate?

Rust network protocol 2633 and build 165217 on Windows is what yaboss1 uses. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is yaboss1 for staying online?

Currently offline, yaboss1 was last seen 33 days 10 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. On 25 September 2026, Rust Data Lab saw it for the first time.

Wipe schedule

What is the wiping pattern on yaboss1?

The record holds too few of yaboss1's wipes to show its rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 33 days 11 hours ago the current world was made.

What does a typical wipe day on yaboss1 involve?

At their busiest, recent wipes averaged 1 players. Peak numbers on the latest wipe came 1 hours in.

Where it appears

What should you understand from the tags yaboss1 carries?

gmrust (Game mode): Standard Rust survival is the game here; mp1 (Max players): It has 1 slots; ts8 (Group limit): This uses the game's default: 8 per team; v2633 (Protocol): Protocol 2633 is required; join only if your game matches it; cs165217 (Build): It runs build 165217; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): The region field is left blank: that is the tag list yaboss1 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 yaboss1 appear in?

These themed Rust Data Lab lists carry yaboss1: Rust community servers, measured. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

How does yaboss1 compare with other servers in the rankings?

Player hours over the last week put yaboss1 at #14,679, inside the top 64% of ranked servers.

How full is yaboss1 right now?

No live signal from yaboss1 right now, which was last seen 33 days 10 hours ago.

Connection

What steps get you onto yaboss1?

Open the console with F1 in Rust and type client.connect 46.72.251.238:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Standard Rust survival is the game here.
mp1
Max players It has 1 slots.
ts8
Group limit This uses the game's default: 8 per team.
v2633
Protocol Protocol 2633 is required; join only if your game matches it.
cs165217
Build It runs build 165217.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code The region field is left blank.

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.