Not ranked yet, so there is no place in the school to report.
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
49/ 100
D
Slipped a little: down 326 places this week. Nothing a good wipe can't fix.
A term to build on.
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
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
You'll find no region listed by Oxide Test Server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 178.168.43.230:28015 is the address to use.
How reliable is Oxide Test Server, and is it up?
You cannot join now: Oxide Test Server is offline, last seen 38 days 19 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 20 September 2026.
What Rust version is Oxide Test Server on?
Rust network protocol 2633 and build 164530 on Linux is what Oxide Test Server runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Oxide Test Server wipe, and how often?
The record holds too few of Oxide Test Server's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 45 days 16 hours.
Population
Where does Oxide Test Server place in the wider field of Rust servers?
In the top – of all ranked servers, Oxide Test Server sits at #13,324 for player hours over the last seven days.
What does the population on Oxide Test Server look like?
Oxide Test Server is offline at the moment; the last time it was seen was 38 days 19 hours ago.
Tags
What is meant by the tags on Oxide Test Server?
The game's browser takes its cue from the tags Oxide Test Server has set: gmrust (Game mode): Rust survival, played by the standard rules; mp4 (Max players): 4 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Oxide Test Server?
These Rust Server Score lists count Oxide Test Server among them: Best community servers, graded. 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.
Map and rules
How is Oxide Test Server set up, and what rules does it keep?
The name of Oxide Test Server gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. You are not covered by VAC, Valve's anti-cheat.
Oxide Test Server runs which map?
A procedural map, generated by the game, is what Oxide Test Server runs.
Getting in
How do you get onto Oxide Test Server?
Enter client.connect 178.168.43.230: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 asmp4,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp4
Max players4 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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.