Station NA-15454 · recording
Deathloop Battlefield | Weekly | Koth | Loadouts
Online NA 66.51.99.58:28010 checked 3m ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,454
- top 70% · #1535 in NA
- Last wipe
- 1d ago
- weekly schedule
- Next wipe
- 5d 0h
- Thu 26 Nov, 13:13 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0■steady+0 players
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 70% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 26 November, 13:13 UTC, in 5d 0h. Its weekly schedule tag · low confidence
- usual gap
- 7 daysbetween real wipes
- on rhythm
- 60%of its recent wipes
- wipe-day peak
- 0players, last three wipes
- crowd held
- 0%else halves by day 1
Coming wipes
- 5d 0hThu 26 Nov, 13:13 UTC
- 12d 5hThu 3 Dec, 19:00 UTCFW
- 19d 0hThu 10 Dec, 13:13 UTC
- 26d 0hThu 17 Dec, 13:13 UTC
- 33d 0hThu 24 Dec, 13:13 UTC
- 40d 0hThu 31 Dec, 13:13 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 19 Nov, 13:13 UTC1d ago | – | – | – | – | running | 0 |
| Thu 12 Nov, 13:13 UTC8d ago | M0.0■steady | 0 | – | 7 days | 0 | |
| Fri 6 Nov, 13:03 UTC14d ago | M0.0■steady | 0 | – | 6 days | 0 | |
| Thu 5 Nov, 18:10 UTC FW15d ago | – | – | – | – | – | 0 |
| Thu 5 Nov, 13:14 UTC15d ago | M0.0■steady | 0 | – | 1 days | 0 | |
| Thu 29 Oct, 13:14 UTC22d ago | M0.0▲rising | 1 | halved by day 1 | 7 days | 0 | |
| Sat 3 Oct, 01:03 UTC49d ago | M0.0■steady | 0 | – | 26.5 days | 0 | |
| Thu 1 Oct, 18:00 UTC FW50d ago | – | – | – | – | – | – |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Deathloop Battlefield | Weekly | Koth | Loadouts?
Deathloop Battlefield | Weekly | Koth | Loadouts runs a procedural map of size 2,400 with seed 138294602, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on Deathloop Battlefield | Weekly | Koth | Loadouts?
No gather rate appears in the name of Deathloop Battlefield | Weekly | Koth | Loadouts. Groups hold up to 8 players, which is the default for the game. In battlefield mode, kits and high rates for fast PvP. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on Deathloop Battlefield | Weekly | Koth | Loadouts?
At this moment, Deathloop Battlefield | Weekly | Koth | Loadouts records 0 players across 50 slots. The seven-day average for this server is 0 players.
How does Deathloop Battlefield | Weekly | Koth | Loadouts rank against other Rust servers?
Deathloop Battlefield | Weekly | Koth | Loadouts is #1,535 in North America and #15,454 worldwide on the past week's player hours, within the top 70% of ranked servers.
Server details
How reliably does Deathloop Battlefield | Weekly | Koth | Loadouts stay online?
Deathloop Battlefield | Weekly | Koth | Loadouts is up at the moment. Going by the uptime figure it reports, it restarted about 21 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. Its earliest appearance in the records of Rust Server Trends dates to 14 September 2026.
Does Deathloop Battlefield | Weekly | Koth | Loadouts hold a steady tick rate?
Its average server fps over the last 48 hours was 5, and it never dropped below 5. The world held up to 29,000 entities at its peak, buildings and deployables included. It reached a ceiling of 1,304 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.
Which region does Deathloop Battlefield | Weekly | Koth | Loadouts run from?
The NA tag is how Deathloop Battlefield | Weekly | Koth | Loadouts lists itself in North America. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 66.51.99.58:28010 is the address it uses.
What build of Rust does Deathloop Battlefield | Weekly | Koth | Loadouts use?
Rust network protocol 2636 and build 127089 on Linux is what Deathloop Battlefield | Weekly | Koth | Loadouts runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on Deathloop Battlefield | Weekly | Koth | Loadouts?
The recent wipes averaged a busiest count of 0 players. The peak on the most recent wipe came 0 hours after the wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell under half by day 1 in the wipes where it didn't hold.
On what timetable does Deathloop Battlefield | Weekly | Koth | Loadouts run its wipes?
The prediction follows its tag, because too few of Deathloop Battlefield | Weekly | Koth | Loadouts's wipes are on record to confirm its schedule. Thursday 26 November at 13:13 UTC is when its next wipe is due. It has run its current world for 47 hours. Its tags state a weekly wipe schedule.
Tags
What do the server tags on Deathloop Battlefield | Weekly | Koth | Loadouts mean?
The game's server browser reads the tags Deathloop Battlefield | Weekly | Koth | Loadouts publishes: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): This uses the game default of 8 per team; v2636 (Protocol): Your game needs to be on protocol 2636 to join; cs127089-84fd9a97663 (Build): The build number is not made public; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^w (Weekly): Wipes happen weekly; ^i (Battlefield): High rates and kits for fast PvP; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; NA (North America): In the server browser it appears under North America. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Deathloop Battlefield | Weekly | Koth | Loadouts appear?
These Rust Server Trends lists include Deathloop Battlefield | Weekly | Koth | Loadouts: Modded Rust servers, tracked live, Rust battlefield servers and North America Rust servers. On the server list, the filters it matches are: 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 3 days.
Join the server
How do you connect to Deathloop Battlefield | Weekly | Koth | Loadouts?
To join, enter client.connect 66.51.99.58:28010 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. https://discord.com/invite/ZUR7CjSE5P is where its website lives.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.