Working its way up from the back of the class: #15,950 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
22/ 100
F
Lost ground: down 8,840 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
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 3 Oct. 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. 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
Future SOLO leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 95.156.213.168:10100.
How reliable is Future SOLO, and is it up?
You cannot join now: Future SOLO is offline, last seen 23 days 11 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 3 October 2026.
On what Rust version does Future SOLO sit?
The server Future SOLO 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.
Wipe cycle
When does Future SOLO wipe, and how often?
Future SOLO has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 26 days 11 hours have passed since this world was made.
Population
Where does Future SOLO place in the wider field of Rust servers?
Over the last seven days, Future SOLO has #15,950 for player hours, in the top 71% of all ranked servers.
What does the population on Future SOLO look like?
Future SOLO is offline at the moment; the last time it was seen was 23 days 11 hours ago.
Tags and filters
What do Future SOLO's tags stand for?
The game's browser takes its cue from the tags Future SOLO has set: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Future SOLO appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Future SOLO among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
How is Future SOLO set up, and what rules does it keep?
You will find no gather rate in the name of Future SOLO. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Future SOLO?
The game generates the procedural map on Future SOLO at size 3,500 with seed 6738. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to Future SOLO?
To connect, start Rust, press F1, and type client.connect 95.156.213.168:10100. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmvanilla,cs166652,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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. Even marks across the subjects, from F to F.