Working its way up from the back of the class: #15,490 on player hours.
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
50/ 100
D
Holding steady: up 106 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 19 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
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
Next wipe Thursday 5 November, 19:00 UTC, in 8d 18h.
The 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
Which region is Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 based in?
No region is published for Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 46.19.66.6:28015.
How dependable is Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026, and is it online at the moment?
You cannot join now: Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 is offline, last seen 38 days 6 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 19 September 2026.
What Rust version is Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 on?
You will find Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 on Rust network protocol 2633 and build 164530, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 wipe its map?
The estimate for Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026's next wipe comes from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 38 days 8 hours. Its tags record that it wipes monthly.
Population
Where does Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 sit among Rust servers?
In the top 69% of all ranked servers, Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 sits at #15,490 for player hours over the last seven days.
What does the population on Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 look like?
The last sighting of Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 was 38 days 6 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026?
gmvanilla (Game mode): You play vanilla survival here; mp200 (Max players): 200 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; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 publishes, and the game's server browser reads them. 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.
Who operates Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026?
Among all the servers we track, only Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 publishes this diamondproject.fun hostname.
Which lists and filters on Rust Server Score show Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026?
These Rust Server Score lists count Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 1x.
Map and rules
Which rules does Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 enforce, and what are its settings?
Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 sets gather at 1x, as its name suggests. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 uses?
The game generates the procedural map on Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026 at size 3,000 with seed 59366347. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How do you get onto Diamond BLUE #2 [X1|NOLIMIT|CLASSIC|FPS+|KITS] - 19.09.2026?
To connect, start Rust, press F1, and type client.connect 46.19.66.6:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2633,^m,gmvanilla,cs164530,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp200
Max players200 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.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).