Working its way up from the back of the class: #15,327 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
52/ 100
D
Moving up: up 650 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
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 71% of all ranked servers, and #383 of the duo servers (top 88%). 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 Sunday 1 November, 10:42 UTC, in 3d 4h.
Weekly: 7 days after its last 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 TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 sit?
TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 82.108.132.34:28015 is the address to use.
Is TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 up, and how steady is its uptime?
At this moment, TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 is offline; the last time it was seen was 15 days 11 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 4 October 2026.
Which Rust version is TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 running?
The server TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 is on Rust network protocol 2634 and build 166652 under Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 reset?
The next wipe on TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 is a projection from weekly: 7 days after its last wipe. Expect the next wipe on Sunday 1 November at 10:42 UTC. The world it runs now was created 24 days 19 hours. Wipes are scheduled weekly, according to its tags.
Player count
Where does TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 sit among Rust servers?
In the top 71% of all ranked servers, TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 sits at #15,327 for player hours over the last seven days. In the duo group, it ranks #383.
What does the population on TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 look like?
It has been 15 days 11 hours since TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 was last seen, and it is offline right now.
Tags
What is meant by 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): A team can hold 2 players at most; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^w (Weekly): It wipes weekly; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^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. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 appear in the Rust Server Score lists and filters?
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. You can find it under these server-list filters: 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?
TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00 sets gather at 2x, as its name suggests. You can have up to 2 players in a group (duo). It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
The game generates a procedural map for TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00.
Connecting
How do you get onto TurboRsut | SOLO/DUO | 2X | Wipe: Friday 18:00?
To connect, start Rust, press F1, and type client.connect 82.108.132.34:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^w,gmrust,cs166652,ts2,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts2
Group limitA team can hold 2 players at most.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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); standing is the one to work on (F).