Working its way up from the back of the class: #15,549 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 404 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is BrowserListNameServer - Oxide By - lox based in?
No region is published for BrowserListNameServer - Oxide By - lox. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 37.212.24.130:28015.
How reliable is BrowserListNameServer - Oxide By - lox, and is it up?
At this moment, BrowserListNameServer - Oxide By - lox is offline; the last time it was seen was 17 days ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 12 October 2026, Rust Server Score saw it for the first time.
Which Rust version is BrowserListNameServer - Oxide By - lox running?
Rust network protocol 2293 on Windows is what BrowserListNameServer - Oxide By - lox runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does BrowserListNameServer - Oxide By - lox wipe, and how often?
There are too few wipes on record for BrowserListNameServer - Oxide By - lox to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 137 days 14 hours.
Population
Where does BrowserListNameServer - Oxide By - lox place in the wider field of Rust servers?
Over the last seven days, BrowserListNameServer - Oxide By - lox has #15,549 for player hours, in the top 71% of all ranked servers.
What does the population on BrowserListNameServer - Oxide By - lox look like?
The last sighting of BrowserListNameServer - Oxide By - lox was 17 days ago, and it is offline right now.
Tags
What is meant by the tags on BrowserListNameServer - Oxide By - lox?
The game's browser takes its cue from the tags BrowserListNameServer - Oxide By - lox has set: gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; v2293 (Protocol): To get in, your game needs to be on the same version: the protocol is 2293; ptrak (Networking): This is RakNet: the network layer Rust normally uses; oxide (Oxide): The plugin framework in use is Oxide (uMod); modded (Modded): Plugins or settings alter the game, so it sits under Modded; h532c2936 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner; stok (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature BrowserListNameServer - Oxide By - lox?
These Rust Server Score lists count BrowserListNameServer - Oxide By - lox among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded.
Server rules
Which rules does BrowserListNameServer - Oxide By - lox enforce, and what are its settings?
The name of BrowserListNameServer - Oxide By - lox gives no gather rate. You will find no published group limit. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. You are not covered by VAC, Valve's anti-cheat.
Getting in
How should you connect to BrowserListNameServer - Oxide By - lox?
Enter client.connect 37.212.24.130:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,v2293,h532c2936,stok,gmrust,oxide,modded
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
v2293
ProtocolTo get in, your game needs to be on the same version: the protocol is 2293.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
Mods and access
oxide
OxideThe plugin framework in use is Oxide (uMod).
modded
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
h532c2936
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
stok
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).