Working its way up from the back of the class: #15,101 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
37/ 100
F
Slipped a little: down 4,056 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (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 70% of all ranked servers, and #374 of the duo servers (top 87%). Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
····W··
··WW···
·······
···
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 Thursday 29 October, 22:08 UTC, in 1d 1h.
Its biweekly schedule tag · low confidence
usual gap1.7 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 4
Coming wipes
1d 1hThu 29 Oct, 22:08 UTC
7d 22hThu 5 Nov, 19:00 UTCFW
15d 1hThu 12 Nov, 22:08 UTC
29d 1hThu 26 Nov, 22:08 UTC
35d 22hThu 3 Dec, 19:00 UTCFW
43d 1hThu 10 Dec, 22:08 UTC
The first 48 hours of its last wipes
Thu 15 OctWed 14 OctFri 9 Oct
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 15 Oct, 22:08 UTC12d ago
0
–
running
1
Wed 14 Oct, 05:52 UTC14d ago
1
–
1.7 days
0
Fri 9 Oct, 09:25 UTC19d ago
1
–
4.9 days
0
Sat 3 Oct, 04:05 UTC25d ago
1
halved by day 4
6.2 days
0
Fri 2 Oct, 10:27 UTC26d ago
1
–
0.7 days
0
Fri 2 Oct, 03:58 UTC26d ago
1
–
0.3 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
In what location does SOLO/DUO/NO CLAN Vanilla 1x sit?
SOLO/DUO/NO CLAN Vanilla 1x leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 104.28.205.73:28015.
How reliable is SOLO/DUO/NO CLAN Vanilla 1x, and is it up?
At this moment, SOLO/DUO/NO CLAN Vanilla 1x is offline; the last time it was seen was 12 days 22 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 30 September 2026, Rust Server Score saw it for the first time.
What Rust version is SOLO/DUO/NO CLAN Vanilla 1x on?
Rust network protocol 2634 and build 167231 on Linux is what SOLO/DUO/NO CLAN Vanilla 1x runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does SOLO/DUO/NO CLAN Vanilla 1x reset?
The prediction follows its tag, because too few of SOLO/DUO/NO CLAN Vanilla 1x's wipes are on record to confirm the schedule. Expect the next wipe on Thursday 29 October at 22:08 UTC. The world it runs now was created 12 days 22 hours. Its tags give a wipe schedule of every two weeks.
What happens on SOLO/DUO/NO CLAN Vanilla 1x when wipe day arrives?
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 4 in the wipes where it did not hold.
Population
What position does SOLO/DUO/NO CLAN Vanilla 1x hold in the rankings?
In the top 70% of all ranked servers, SOLO/DUO/NO CLAN Vanilla 1x sits at #15,101 for player hours over the last seven days. In the duo group, it ranks #374.
What does the population on SOLO/DUO/NO CLAN Vanilla 1x look like?
SOLO/DUO/NO CLAN Vanilla 1x is offline at the moment; the last time it was seen was 12 days 22 hours ago.
Lists and filters
How should you read the tags on SOLO/DUO/NO CLAN Vanilla 1x?
The game's browser takes its cue from the tags SOLO/DUO/NO CLAN Vanilla 1x has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts2 (Group limit): A team can hold 2 players at most; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167231 (Build): Build number: 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Which lists and filters on Rust Server Score show SOLO/DUO/NO CLAN Vanilla 1x?
Rust Server Score lists that include SOLO/DUO/NO CLAN Vanilla 1x: Duo servers, marked like a report and Modded Rust servers, graded. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 1x.
Rules and settings
How is SOLO/DUO/NO CLAN Vanilla 1x set up, and what rules does it keep?
Going by its name, SOLO/DUO/NO CLAN Vanilla 1x runs 1x gather. The cap on group size is 2 players (duo). You get survival here, 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. Plugins on it number Oxide. Vanilla is what it calls itself: you get the unmodified game: no rate changes, no kits, no rule changes. You are covered by VAC, Valve's anti-cheat.
Which map is in play on SOLO/DUO/NO CLAN Vanilla 1x?
The game generates a procedural map for SOLO/DUO/NO CLAN Vanilla 1x.
Connecting
What is the way to join SOLO/DUO/NO CLAN Vanilla 1x?
To connect, start Rust, press F1, and type client.connect 104.28.205.73: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,^b,^v,gmrust,cs167231,ts2,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts2
Group limitA team can hold 2 players at most.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167231
BuildBuild number: 167231.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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 (F); wipes are the one to work on (F).