On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#10,893top 49% · #1306 in NA
Last wipe9h agoweekly schedule
Next wipe6d 20hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
51/ 100
D
Working its way up from the back of the class: #10,893 on player hours.
Uptimehours on the list, last 48
81/ 100
B+
Missed a few lessons: on the list 39 of the last 48 hours.
Performanceserver fps, last 48 hours
16/ 100
F
Needs to work on its frame rate: 10 server fps on average.
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.
A term to build on.
Strongest in uptime (B+); population 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
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 49% of all ranked servers, top 70% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
···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 Thursday 5 November, 19:00 UTC, in 6d 20h.
The force wipe · high confidence
usual gap26.5 daysbetween real wipes
wipe-day peak0players, last three wipes
Coming wipes
6d 20hThu 5 Nov, 19:00 UTCFW
13d 14hThu 12 Nov, 13:14 UTC
20d 14hThu 19 Nov, 13:14 UTC
27d 14hThu 26 Nov, 13:14 UTC
34d 20hThu 3 Dec, 19:00 UTCFW
41d 14hThu 10 Dec, 13:14 UTC
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
Thu 29 Oct, 13:14 UTC9h ago
–
–
running
0
Sat 3 Oct, 01:03 UTC26d ago
0
–
–
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
Where in the world is Deathloop Battlefield | Weekly | Koth | Loadouts?
You'll see Deathloop Battlefield | Weekly | Koth | Loadouts listed in North America, tagged NA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 66.51.99.58:28010.
Is Deathloop Battlefield | Weekly | Koth | Loadouts up, and how steady is its uptime?
Right now, Deathloop Battlefield | Weekly | Koth | Loadouts is online. About 7 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 17 of 168 hours, or 10% of the time. On 14 September 2026, Rust Server Score saw it for the first time.
The average over the last 48 hours was 10 server fps, and it never went below 5. Up to 39,371 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 1,906 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does Deathloop Battlefield | Weekly | Koth | Loadouts sit?
The server Deathloop Battlefield | Weekly | Koth | Loadouts is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Deathloop Battlefield | Weekly | Koth | Loadouts wipe, and how often?
Its tag sets the prediction, as the record holds too few of Deathloop Battlefield | Weekly | Koth | Loadouts's wipes to confirm its schedule. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 9 hours. The tags carry a weekly wipe schedule.
What happens on Deathloop Battlefield | Weekly | Koth | Loadouts when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does Deathloop Battlefield | Weekly | Koth | Loadouts sit among Rust servers?
In North America, Deathloop Battlefield | Weekly | Koth | Loadouts is #1,306, and overall it is #10,893 on player hours over the last seven days, in the top 49% of all ranked servers.
Is Deathloop Battlefield | Weekly | Koth | Loadouts a busy server?
Right now, 0 players are on Deathloop Battlefield | Weekly | Koth | Loadouts, which has 50 slots. It peaked at 1 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 07:00 UTC, with an average of 1 players.
Lists and filters
What do Deathloop Battlefield | Weekly | Koth | Loadouts's tags stand for?
The game's browser takes its cue from the tags Deathloop Battlefield | Weekly | Koth | Loadouts has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^i (Battlefield): PvP runs fast here, with kits and boosted rates; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; NA (North America): In the server browser it appears under North America. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Deathloop Battlefield | Weekly | Koth | Loadouts appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Deathloop Battlefield | Weekly | Koth | Loadouts among them: Modded Rust servers, graded, Rust battlefield servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Modded; Server tag: Weekly ^w, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours.
Rules and settings
How is Deathloop Battlefield | Weekly | Koth | Loadouts set up, and what rules does it keep?
The name of Deathloop Battlefield | Weekly | Koth | Loadouts gives no gather rate. The group limit stays at the game's default of 8 players. You get battlefield here, kits and high rates for fast PvP. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Deathloop Battlefield | Weekly | Koth | Loadouts uses?
Deathloop Battlefield | Weekly | Koth | Loadouts runs a game-generated procedural map at size 2,400, seed 1376975975. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto Deathloop Battlefield | Weekly | Koth | Loadouts?
To connect, start Rust, press F1, and type client.connect 66.51.99.58:28010. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/ZUR7CjSE5P.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^w,^i,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Gameplay
^i
BattlefieldPvP runs fast here, with kits and boosted rates.
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.
Region
NA
North AmericaIn the server browser it appears under North America.
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 uptime (B+); population is the one to work on (F).