Working its way up from the back of the class: #14,977 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
45/ 100
D
Slipped a little: down 1,533 places this week. Nothing a good wipe can't fix.
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.
AveragePeak
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 66% of all ranked servers. Ranked on player hours over the last seven days.
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
from its schedule tag
Next wipe Friday 30 October, 15:48 UTC, in 2d 16h.
Its biweekly schedule tag · low confidence
wipe-day peak1players, last three wipes
Coming wipes
2d 16hFri 30 Oct, 15:48 UTC
8d 19hThu 5 Nov, 19:00 UTCFW
16d 16hFri 13 Nov, 15:48 UTC
30d 16hFri 27 Nov, 15:48 UTC
36d 19hThu 3 Dec, 19:00 UTCFW
44d 16hFri 11 Dec, 15:48 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 15:48 UTC25d ago
1
–
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
..... leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 14.47.104.48:28015 is the address to use.
How dependable is ....., and is it online at the moment?
At this moment, ..... is offline; the last time it was seen was 25 days 4 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
On what Rust version does ..... sit?
You will find ..... on Rust network protocol 2634 and build 166586, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does ..... wipe its map?
Its tag sets the prediction, as the record holds too few of .....'s wipes to confirm its schedule. Friday 30 October at 15:48 UTC is the date set for its next wipe. 25 days 6 hours have passed since this world was made. Its tags give a wipe schedule of every two weeks.
What should you expect from wipe day on .....?
Across its recent wipes, the busiest moments averaged 1 players. 2 hours after the latest wipe began, the crowd hit its peak.
Population
Where does ..... sit among Rust servers?
Over the last seven days, ..... has #14,977 for player hours, in the top 66% of all ranked servers.
Is ..... a busy server?
The last sighting of ..... was 25 days 4 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on .....?
gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): Its slot count is 0; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166586 (Build): Build number: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^b (Biweekly): Every two weeks it wipes; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags ..... 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.
Where does ..... appear in the Rust Server Score lists and filters?
These Rust Server Score lists count ..... among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Server rules
What settings and rules apply on .....?
The name of ..... gives no gather rate. The group limit stays at the game's default of 8 players. pve is the mode here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
..... runs which map?
..... runs a game-generated procedural map at size 4,000, seed 1756347205. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How do you get onto .....?
Enter client.connect 14.47.104.48:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/BCnQzM6zhC.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2634,^b,^p,gmrust,cs166586,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp0
Max playersIts slot count is 0.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166586
BuildBuild number: 166586.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).