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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
AveragePeakWipe
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
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, 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
Peak
Crowd
Lasted
Players before
Wed 16 Sep, 22:51 UTC41d ago
0
–
running
0
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 Rust with Oxide smoke 20260916044956-p1 based in?
No region is published for Rust with Oxide smoke 20260916044956-p1. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 47.187.141.239:29015 is the address to use.
Is Rust with Oxide smoke 20260916044956-p1 up, and how steady is its uptime?
At this moment, Rust with Oxide smoke 20260916044956-p1 is offline; the last time it was seen was 41 days 5 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 16 September 2026.
On what Rust version does Rust with Oxide smoke 20260916044956-p1 sit?
You will find Rust with Oxide smoke 20260916044956-p1 on Rust network protocol 2632 and build 161125, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does Rust with Oxide smoke 20260916044956-p1 wipe its map?
Rust with Oxide smoke 20260916044956-p1 has not had enough wipes recorded to reveal its 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 41 days 8 hours.
What should you expect from wipe day on Rust with Oxide smoke 20260916044956-p1?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Player count
Where does Rust with Oxide smoke 20260916044956-p1 place in the wider field of Rust servers?
In the top – of all ranked servers, Rust with Oxide smoke 20260916044956-p1 sits at #15,512 for player hours over the last seven days.
What does the population on Rust with Oxide smoke 20260916044956-p1 look like?
Rust with Oxide smoke 20260916044956-p1 is offline at the moment; the last time it was seen was 41 days 5 hours ago.
Lists and filters
How should you read the tags on Rust with Oxide smoke 20260916044956-p1?
You'll see Rust with Oxide smoke 20260916044956-p1 tagged with gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2632 (Protocol): To get in, your game needs to be on the same version: the protocol is 2632; cs161125 (Build): The game build is 161125; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Rust with Oxide smoke 20260916044956-p1 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Rust with Oxide smoke 20260916044956-p1 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Rust with Oxide smoke 20260916044956-p1?
You will find no gather rate in the name of Rust with Oxide smoke 20260916044956-p1. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Rust with Oxide smoke 20260916044956-p1 runs which map?
The game generates a procedural map for Rust with Oxide smoke 20260916044956-p1.
How to join
How should you connect to Rust with Oxide smoke 20260916044956-p1?
To connect, start Rust, press F1, and type client.connect 47.187.141.239:29015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2632
ProtocolTo get in, your game needs to be on the same version: the protocol is 2632.
cs161125
BuildThe game build is 161125.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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.
Not enough figures yet to write a report. Check back after a few days on the list.