Station XX-15032 · no signal
BrowserListNameServer - Oxide By - lox
Offline 37.212.31.175:28015 checked 6d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak 1
- Rank
- #15,032
- top 68%
- Last wipe
- 136d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M –not enough readings
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 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not 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 |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 settings and rules apply on BrowserListNameServer - Oxide By - lox?
The name of BrowserListNameServer - Oxide By - lox gives no gather rate. It gives no group limit in its listing. In survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. The server has VAC off, Valve's anti-cheat.
Population
What is the current population on BrowserListNameServer - Oxide By - lox?
A reading taken now finds BrowserListNameServer - Oxide By - lox offline; the most recent activity was 6 days 9 hours ago. Averaged across the last seven days the population was 0 players, reaching a peak of 1.
How does BrowserListNameServer - Oxide By - lox rank against other Rust servers?
On player hours for the past week, BrowserListNameServer - Oxide By - lox sits at #15,032, which puts it inside the top 68% of every ranked server.
Server facts
How reliably does BrowserListNameServer - Oxide By - lox stay online?
No contact with BrowserListNameServer - Oxide By - lox right now, and the last recorded contact was 6 days 9 hours ago. 2 of 168 hours in the last 7 full days were up time, 1% of the total. 19 October 2026 is when Rust Server Trends first recorded it.
Where in the world is BrowserListNameServer - Oxide By - lox hosted?
No region is published by BrowserListNameServer - Oxide By - lox. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 37.212.31.175:28015.
What build of Rust does BrowserListNameServer - Oxide By - lox use?
Rust network protocol 2293 on Windows is what BrowserListNameServer - Oxide By - lox runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
How often does BrowserListNameServer - Oxide By - lox wipe, and on which days?
The rhythm of BrowserListNameServer - Oxide By - lox 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. 136 days 5 hours is how long the current world has been running.
Server tags
What do the server tags on BrowserListNameServer - Oxide By - lox mean?
The game's server browser reads the tags BrowserListNameServer - Oxide By - lox publishes: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): 100 slots are available; v2293 (Protocol): To connect, your game must be on the same protocol, 2293; ptrak (Networking): The network layer is RakNet, the game's standard; oxide (Oxide): Oxide (uMod) is the plugin framework running here; modded (Modded): The game is changed by plugins or settings, placing it under Modded; h532c2936 (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags; stok (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. 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 BrowserListNameServer - Oxide By - lox appear?
You will find BrowserListNameServer - Oxide By - lox on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded.
How to join
How do you connect to BrowserListNameServer - Oxide By - lox?
Enter client.connect 37.212.31.175: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.