Rust Data LabData lab · live
Live readings Servers11,648 Players32,263 Populated2,789 Fresh wipes · 3h72 Sampled every 5 min

Element card · group Modded · atomic number 16,954, its rank

BrowserListNameServer - Oxide By - lox

Offline 46.150.17.118:28015 checked 30d ago

moddedcarbon
Join the experiment
Atomic mass · players now 0/ 100 0% full Room to join
7-day average0peak –
Rank · atomic number#16,954top 71%
Last wipe30d 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
15k10k15k20k28 Sep29 Sep1 Oct2 Oct4 Oct5 Oct

Top 71% 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 peak0players, last three wipes

The first 48 hours of its last wipes

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

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 08:28 UTC30d ago 0 – 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 Sh ShockRust | Bl… 33
    ShockRust | Blue | NoLimit no group limit · 153 on average 33/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 120
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 120/ 100
  3. 3 Re RETRO RUST #1 … 52
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average 52/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 13
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 13/ 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Х|ДЛ… 3
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 3/ 1,000

Quick answers

from the figures on this page

Settings and map

What settings and rules apply on BrowserListNameServer - Oxide By - lox?

No gather rate appears in the name of BrowserListNameServer - Oxide By - lox. No group limit is published. survival is the game mode, raiding, building and gathering: the standard game. Raids and player fights are part of play here. In the server browser it sits under Modded: the game is changed by plugins or settings. Carbon plugins are running on it. VAC is off, Valve's anti-cheat.

About the server

What region hosts BrowserListNameServer - Oxide By - lox?

Nothing about a region is published by BrowserListNameServer - Oxide By - lox. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 46.150.17.118:28015 is the address it uses.

On what Rust version does BrowserListNameServer - Oxide By - lox operate?

On Windows, BrowserListNameServer - Oxide By - lox is running Rust network protocol 2388 and build 81925. The protocol must match for you to join; Steam will update your game.

Does BrowserListNameServer - Oxide By - lox stay up, and how reliable is its uptime?

BrowserListNameServer - Oxide By - lox is not online at the moment; the last sighting was 30 days 19 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. On 28 September 2026, Rust Data Lab saw it for the first time.

Wipe days

How often does a wipe happen on BrowserListNameServer - Oxide By - lox, and at what time?

The record holds too few of BrowserListNameServer - Oxide By - lox'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. The world it is running now dates from 30 days 19 hours ago.

How does BrowserListNameServer - Oxide By - lox look on the day of a wipe?

At their busiest, recent wipes averaged 0 players. The latest wipe's peak fell 0 hours after it began.

Lists and tags

What should you understand from the tags BrowserListNameServer - Oxide By - lox carries?

These are the tags BrowserListNameServer - Oxide By - lox makes public for the server browser to read: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): It has 100 slots; v2388 (Protocol): To join, your game must match protocol 2388; cs81925 (Build): The game build is 81925; ptrak (Networking): This runs on RakNet, the standard layer; ^z (Modded): You will find it under Modded: the game is altered by plugins or settings; ^y (Carbon): The plugin framework here is Carbon; hb9a1b1a2 (Custom tag): Not a standard Rust tag, so either a plugin or the owner applied it; stok (Custom tag): Not a standard Rust tag, so either a plugin or the owner applied it. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Which Rust Data Lab filters and lists does BrowserListNameServer - Oxide By - lox appear in?

You will find BrowserListNameServer - Oxide By - lox 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 Carbon ^y.

Population

How does BrowserListNameServer - Oxide By - lox compare with other servers in the rankings?

BrowserListNameServer - Oxide By - lox sits at #16,954 for seven-day player hours, placing it in the top 71% of ranked servers.

How full is BrowserListNameServer - Oxide By - lox right now?

BrowserListNameServer - Oxide By - lox is offline at the moment; the last sighting was 30 days 19 hours ago.

Connection

How can you connect to BrowserListNameServer - Oxide By - lox?

In Rust, press F1 and enter client.connect 46.150.17.118:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

Published as mp100,ptrak,v2388,hb9a1b1a2,stok,gmrust,cs81925,^z,^y

Game

gmrust
Game mode Survival in the standard Rust style.
mp100
Max players It has 100 slots.
v2388
Protocol To join, your game must match protocol 2388.
cs81925
Build The game build is 81925.
ptrak
Networking This runs on RakNet, the standard layer.

Mods and access

^z
Modded You will find it under Modded: the game is altered by plugins or settings.
^y
Carbon The plugin framework here is Carbon.

Other

hb9a1b1a2
Custom tag Not a standard Rust tag, so either a plugin or the owner applied it.
stok
Custom tag Not a standard Rust tag, so either a plugin or the owner applied it.

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.