Working its way up from the back of the class: #16,949 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
47/ 100
D
Slipped a little: down 1,062 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); wipes are 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
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
······W
····W·W
···W···
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap4.5 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1.5
The first 48 hours of its last wipes
Thu 24 SepSun 20 SepFri 18 Sep
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 24 Sep, 19:12 UTC34d ago
0
–
running
0
Sun 20 Sep, 06:50 UTC38d ago
1
halved by day 1
4.5 days
0
Fri 18 Sep, 07:31 UTC40d ago
2
–
2 days
0
Sun 13 Sep, 20:21 UTC45d ago
2
halved by day 2
4.5 days
1
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 [NA] Territory War | Kill the Boss to Become the Boss based in?
No region tag appears for [NA] Territory War | Kill the Boss to Become the Boss, but the name suggests North America. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 148.113.182.254:28015.
Is [NA] Territory War | Kill the Boss to Become the Boss up, and how steady is its uptime?
You cannot join now: [NA] Territory War | Kill the Boss to Become the Boss is offline, last seen 31 days 15 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is [NA] Territory War | Kill the Boss to Become the Boss on?
You will find [NA] Territory War | Kill the Boss to Become the Boss on Rust network protocol 2633 and build 165217, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does [NA] Territory War | Kill the Boss to Become the Boss wipe, and how often?
No next wipe can be predicted for [NA] Territory War | Kill the Boss to Become the Boss, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 34 days 4 hours.
What should you expect from wipe day on [NA] Territory War | Kill the Boss to Become the Boss?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 1.5 in the wipes where it did not hold.
Player numbers
Where does [NA] Territory War | Kill the Boss to Become the Boss place in the wider field of Rust servers?
Over the last seven days, [NA] Territory War | Kill the Boss to Become the Boss has #16,949 for player hours, in the top 72% of all ranked servers.
How many players does [NA] Territory War | Kill the Boss to Become the Boss usually have?
It has been 31 days 15 hours since [NA] Territory War | Kill the Boss to Become the Boss was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on [NA] Territory War | Kill the Boss to Become the Boss?
The game's browser takes its cue from the tags [NA] Territory War | Kill the Boss to Become the Boss has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp60 (Max players): Its slot count is 60; ts5 (Group limit): Teams cap out at 5; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Carbon provides the plugin framework here. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [NA] Territory War | Kill the Boss to Become the Boss appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [NA] Territory War | Kill the Boss to Become the Boss among them: Modded Rust servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
How is [NA] Territory War | Kill the Boss to Become the Boss set up, and what rules does it keep?
Nothing in the name of [NA] Territory War | Kill the Boss to Become the Boss states a gather rate. You can play in groups of up to 5 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
Which map is in play on [NA] Territory War | Kill the Boss to Become the Boss?
[NA] Territory War | Kill the Boss to Become the Boss runs a game-generated procedural map at size 4,250, seed 1461847816. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to [NA] Territory War | Kill the Boss to Become the Boss?
Enter client.connect 148.113.182.254:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp60,ptrak,$r?,v2633,gmrust,cs165217,ts5,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp60
Max playersIts slot count is 60.
ts5
Group limitTeams cap out at 5.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonCarbon provides the plugin framework here.
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); wipes are the one to work on (F).