My Oxide Server
Offline 14.56.183.71:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
100% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe 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
the same kind of game, then region, group limit, rate and wipes- 320/350
- 21/250
- 38/250
- 139/200
- 53/200
- 56/100
Quick answers
from the figures on this pageWipe schedule
What wipe timing does My Oxide Server follow?
To tell the rhythm of My Oxide Server, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 52 days 12 hours ago.
Lists and filters
How should you read the tags on My Oxide Server?
These are the tags My Oxide Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show My Oxide Server?
These Rust Metrics lists carry My Oxide Server: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
What player count does My Oxide Server carry?
My Oxide Server is not responding; status offline, last seen 44 days 19 hours ago.
Server details
Which location does My Oxide Server run from?
No region comes from My Oxide Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 14.56.183.71:28015.
What Rust version is My Oxide Server on?
Reading: My Oxide Server, Rust network protocol 2633 and build 163794, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is My Oxide Server up, and how often does it stay up?
Check: connection. My Oxide Server is offline at this moment. Last contact was 44 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Rules and settings
How is My Oxide Server configured, and what rules are in force?
Check: gather rate. The name My Oxide Server does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
What map is My Oxide Server on?
Procedural map on My Oxide Server, made by the game's generator.
Connection
How do you connect to My Oxide Server?
Press F1 in Rust and enter client.connect 14.56.183.71:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.