On the class lists: F (31), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,338top 69% · #1510 in NA
Last wipe482d agobiweekly schedule
Next wipe7d 10hThu 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 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,338 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); 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
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 23 Oct. 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, top 81% in NA. 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 7d 10h.
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
In what location does [US] Badlands 3X Bi-Weekly sit?
You'll see [US] Badlands 3X Bi-Weekly listed in North America, tagged NA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 173.188.36.35:28115.
Is [US] Badlands 3X Bi-Weekly up, and how steady is its uptime?
At this moment, [US] Badlands 3X Bi-Weekly is offline; the last time it was seen was 3 days 22 hours ago. For the last 5 full days, it was up 7 of 120 hours, or 6% of the time. The first sighting by Rust Server Score was on 23 October 2026.
On what Rust version does [US] Badlands 3X Bi-Weekly sit?
Rust network protocol 2592 and build 124915 on Linux is what [US] Badlands 3X Bi-Weekly runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does [US] Badlands 3X Bi-Weekly wipe, and how often?
the force wipe gives the basis for estimating [US] Badlands 3X Bi-Weekly's next wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 482 days 13 hours. Its tags give a wipe schedule of every two weeks.
Player count
Where does [US] Badlands 3X Bi-Weekly place in the wider field of Rust servers?
In North America, [US] Badlands 3X Bi-Weekly is #1,510, and overall it is #15,338 on player hours over the last seven days, in the top 69% of all ranked servers.
Is [US] Badlands 3X Bi-Weekly a busy server?
It has been 3 days 22 hours since [US] Badlands 3X Bi-Weekly was last seen, and it is offline right now. A seven-day average of 0 players applies here.
Tags and filters
How should you read the tags on [US] Badlands 3X Bi-Weekly?
You'll see [US] Badlands 3X Bi-Weekly tagged with gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): The server holds 100 slots; v2592 (Protocol): Join only if your game runs protocol 2592; cs124915 (Build): The game build is 124915; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): The server wipes on a two-week cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): In the server browser it appears under North America in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature [US] Badlands 3X Bi-Weekly?
Rust Server Score lists that include [US] Badlands 3X Bi-Weekly: 3x Rust servers, graded, Modded Rust servers, graded and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Wipe schedule: Every two weeks; Gather rate: 3x.
Server rules
How is [US] Badlands 3X Bi-Weekly set up, and what rules does it keep?
[US] Badlands 3X Bi-Weekly sets gather at 3x, as its name suggests. No group limit is published. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on [US] Badlands 3X Bi-Weekly?
A procedural map of size 4,500 and seed 564942299, generated by the game, is what [US] Badlands 3X Bi-Weekly runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
What is the way to join [US] Badlands 3X Bi-Weekly?
Enter client.connect 173.188.36.35:28115 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://www.badlandsrust.com.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2592,^b,NA,gmrust,cs124915,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersThe server holds 100 slots.
v2592
ProtocolJoin only if your game runs protocol 2592.
cs124915
BuildThe game build is 124915.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under 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 standing (F); population is the one to work on (F).