On the class lists: F (20), with population over 48 hours and no performance mark.
Players now1/ 425% full
7-day average1peak 1
Rank#13,093top 59%
Last wipe17d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
25/ 100
F
A quiet classroom so far: 1 of 4 on average. Plenty of space to grow.
Standingrank on player hours
41/ 100
F
Working its way up from the back of the class: #13,093 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); 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.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 59% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
······W
W··W·WW
·······
·······
····
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 gap1.8 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Sun 11 OctSat 10 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 4, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 11 Oct, 20:25 UTC17d ago
4
–
running
1
Sat 10 Oct, 01:20 UTC19d ago
4+1 queue
–
1.8 days
2
Thu 8 Oct, 21:23 UTC20d ago
4+1 queue
–
1.2 days
1
Mon 5 Oct, 23:15 UTC23d ago
3
halved by day 1
2.9 days
1
Sun 4 Oct, 05:26 UTC25d ago
3
–
1.7 days
1
Thu 17 Sep, 22:33 UTC41d ago
1
–
16.3 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
EU · groups of 300+ · 2x · weekly · 314 on average
48 / 1000
Quick answers
from the figures on this page
Server facts
In what location does 2x 7 day challenge sit?
You'll find no region listed by 2x 7 day challenge. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 68.11.179.74:28015.
How reliable is 2x 7 day challenge, and is it up?
The server is down: 2x 7 day challenge is offline now, with the last sighting 4 days 10 hours ago. For the last 7 full days, it was up 1 of 168 hours, or 1% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is 2x 7 day challenge on?
You will find 2x 7 day challenge on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does 2x 7 day challenge wipe its map?
2x 7 day challenge wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 17 days 10 hours.
What happens on 2x 7 day challenge when wipe day arrives?
The average peak on its recent wipes was 4 players. Peak numbers came 1 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. In the other wipes it slipped under half by day 1.
Population
What position does 2x 7 day challenge hold in the rankings?
Over the last seven days, 2x 7 day challenge has #13,093 for player hours, in the top 59% of all ranked servers.
How many players does 2x 7 day challenge usually have?
It has been 4 days 10 hours since 2x 7 day challenge was last seen, and it is offline right now. Averaging 1 players over seven days, it peaked at 1.
Tags and filters
What do 2x 7 day challenge's tags stand for?
The game's browser takes its cue from the tags 2x 7 day challenge has set: gmvanilla (Game mode): Survival, vanilla style; mp4 (Max players): 4 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. 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 2x 7 day challenge?
These Rust Server Score lists count 2x 7 day challenge among them: 2x Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
Server rules
How is 2x 7 day challenge set up, and what rules does it keep?
2x 7 day challenge sets gather at 2x, as its name suggests. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. 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 2x 7 day challenge uses?
The game generates a procedural map for 2x 7 day challenge.
Getting in
How do you get onto 2x 7 day challenge?
Enter client.connect 68.11.179.74: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 asmp4,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp4
Max players4 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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 standing (F); wipes are the one to work on (F).