Station XX-15290 · no signal
oxide-test
Offline 146.59.45.106:28315 checked 2d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,290
- top 69%
- Last wipe
- 2d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 4 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 1.9 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 27 Oct, 17:33 UTC2d ago | M0.0■steady | 0 | – | – | running | 0 |
| Sun 25 Oct, 19:20 UTC4d ago | M0.0■steady | 0 | – | 1.9 days | 0 |
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 pageServer rules
Which map is running on oxide-test?
The map on oxide-test is procedural, produced by the game.
Which settings and rules apply on oxide-test?
The name of oxide-test gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on oxide-test right now?
oxide-test is not responding at this moment and is offline, last seen 2 days 5 hours ago. The seven-day average for this server is 0 players.
How does oxide-test rank against other Rust servers?
The last seven days of player hours place oxide-test at #15,290, in the top 69% of all ranked servers.
Server facts
How reliably does oxide-test stay online?
oxide-test is down at the moment; the last recorded contact was 2 days 5 hours ago. 2 of 96 hours in the last 4 full days were up time, 2% of the total. On 24 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is oxide-test hosted?
Nothing about a region comes from oxide-test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 146.59.45.106:28315.
Which Rust version is oxide-test running?
oxide-test is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on oxide-test?
The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does oxide-test run its wipes?
The rhythm of oxide-test cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 2 days 5 hours.
Tags
What do the server tags on oxide-test mean?
The game's server browser reads the tags oxide-test publishes: gmrust (Game mode): The game mode is standard Rust survival; mp4 (Max players): Slots: 4; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does oxide-test appear?
You will find oxide-test on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Join the server
What steps get you onto oxide-test?
You can connect by pressing F1 in Rust and typing client.connect 146.59.45.106:28315 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.