BrowserListNameServer - Oxide By - lox
Offline 176.64.84.240:28015 checked 4d ago
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
Top 69% 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
| 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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Settings and map
What settings and rules does BrowserListNameServer - Oxide By - lox run?
No gather rate appears in the name BrowserListNameServer - Oxide By - lox. No group limit is published. Filed under survival, gather, build and raid: the standard game. Fighting and raiding other players is permitted. It is listed under Community in the server browser and is a community server. VAC, Valve's anti-cheat, is disabled.
Tags and filters
Where does BrowserListNameServer - Oxide By - lox appear among the Rust Server Index lists and filters?
These lists on Rust Server Index take BrowserListNameServer - Oxide By - lox: Community Rust servers, indexed. Filed under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last week.
Which tags are attached to BrowserListNameServer - Oxide By - lox, and what do they stand for?
These are the tags BrowserListNameServer - Oxide By - lox publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): Player cap: 100; v2279 (Protocol): Joining needs you on game protocol 2279; ptrak (Networking): The standard RakNet layer carries the connection; hab366af3 (Custom tag): This one is not a standard Rust tag; an owner or plugin put it there; stok (Custom tag): This one is not a standard Rust tag; an owner or plugin put it there. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipe schedule
When does BrowserListNameServer - Oxide By - lox wipe?
BrowserListNameServer - Oxide By - lox's rhythm cannot be told yet: too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The world it runs now was made 4 days 4 hours.
Population
What position does BrowserListNameServer - Oxide By - lox hold among Rust servers?
The seven-day player-hours ranking places BrowserListNameServer - Oxide By - lox at #15,335, among the top 69% of ranked servers.
What does the player count on BrowserListNameServer - Oxide By - lox look like?
The last check found BrowserListNameServer - Oxide By - lox offline, last seen 4 days 4 hours ago. Filed under seven-day average: 0 players.
Operator and status
What Rust version is BrowserListNameServer - Oxide By - lox on?
Rust network protocol 2279 on Windows is what you will find on BrowserListNameServer - Oxide By - lox. The protocol must match before you can join, and Steam takes care of updating it.
Is BrowserListNameServer - Oxide By - lox reachable, and does it stay up?
As of now BrowserListNameServer - Oxide By - lox is offline, with its last appearance 4 days 4 hours ago. Uptime for the last 3 full days came to 0%, 0 hours out of 72. The earliest sighting at Rust Server Index is 25 October 2026.
Where in the world is BrowserListNameServer - Oxide By - lox hosted?
No region is published by BrowserListNameServer - Oxide By - lox. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 176.64.84.240:28015.
Joining the server
What steps lead onto BrowserListNameServer - Oxide By - lox?
Two ways in. Type client.connect 176.64.84.240:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp100,ptrak,v2279,hab366af3,stok,gmrust
Game
gmrust
mp100
v2279
ptrak
Other
hab366af3
stok
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.