On the class lists: F (21), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#14,159top 65%
Last wipe23d agoweekly schedule
Next wipe4d 14hSun 1 Nov, 10:42 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
unmarked
–
No weekly average to mark yet.
Standingrank on player hours
35/ 100
F
Working its way up from the back of the class: #14,159 on player hours.
Uptimehours on the list, last 48
2/ 100
F
Attendance needs work: on the list only 1 of the last 48 hours.
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
48/ 100
D
Slipped a little: down 478 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); uptime 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.
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 65% of all ranked servers, and #368 of the duo servers (top 85%). 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 Sunday 1 November, 10:42 UTC, in 4d 14h.
Its weekly schedule tag · low confidence
usual gap7.7 daysbetween real wipes
wipe-day peak1players, last three wipes
Coming wipes
4d 14hSun 1 Nov, 10:42 UTC
8d 22hThu 5 Nov, 19:00 UTCFW
11d 14hSun 8 Nov, 10:42 UTC
18d 14hSun 15 Nov, 10:42 UTC
25d 14hSun 22 Nov, 10:42 UTC
32d 14hSun 29 Nov, 10:42 UTC
36d 22hThu 3 Dec, 19:00 UTCFW
39d 14hSun 6 Dec, 10:42 UTC
The first 48 hours of its last wipes
Sun 4 OctSat 26 Sep
Players each hour, from the hour of the wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 10:42 UTC23d ago
–
–
running
1
Sat 26 Sep, 17:26 UTC31d ago
1
–
7.7 days
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
Which region is TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 based in?
TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 109.95.72.244:28015.
How reliable is TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00, and is it up?
You can join now: TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 is online. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 25 September 2026, Rust Server Score saw it for the first time.
On what Rust version does TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 sit?
Rust network protocol 2635 and build 168909 on Windows is what TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 reset?
Too few wipes on TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 are recorded to confirm the schedule, so its tag guides the prediction. It is due to wipe next on Sunday 1 November at 10:42 UTC. The world it runs now was created 23 days 9 hours. The tags carry a weekly wipe schedule.
What should you expect from wipe day on TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00?
Across its recent wipes, the busiest moments averaged 1 players.
Player count
Where does TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 place in the wider field of Rust servers?
In the top 65% of all ranked servers, TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 sits at #14,159 for player hours over the last seven days. In the duo group, it ranks #368.
Is TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 a busy server?
TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 is showing 0 players right now, with 50 slots in total.
Tags
How should you read the tags on TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts2 (Group limit): No team may go above 2; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): It wipes weekly; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00?
These Rust Server Score lists count TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 among them: 2x Rust servers, graded, Duo servers, marked like a report and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Weekly; Gather rate: 2x.
Rules and settings
How is TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 set up, and what rules does it keep?
The name of TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 points to a 2x gather rate. You can have up to 2 players in a group (duo). survival is the mode here, gather and build and raid: 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Which map is in play on TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00?
A procedural map, generated by the game, is what TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 runs.
Connecting
What is the way to join TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00?
Enter client.connect 109.95.72.244: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 asmp50,ptrak,$r?,v2635,^w,gmrust,cs168909,ts2,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts2
Group limitNo team may go above 2.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under 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 momentum (D); uptime is the one to work on (F).