Working its way up from the back of the class: #13,065 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
27/ 100
F
Lost ground: down 6,060 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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 60% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·WW····
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap0.8 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Wed 14 OctTue 13 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 14 Oct, 11:07 UTC13d ago
1
–
running
0
Tue 13 Oct, 15:24 UTC14d ago
1
–
0.8 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
No region is published for Forkes Testserver. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 84.134.57.199:28015.
Is Forkes Testserver up, and how steady is its uptime?
You cannot join now: Forkes Testserver is offline, last seen 9 days 15 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 13 October 2026.
Which Rust version is Forkes Testserver running?
Rust network protocol 2634 and build 167781 on Windows is what Forkes Testserver runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does Forkes Testserver wipe its map?
The record holds too few of Forkes Testserver's wipes to tell its rhythm. 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 13 days 13 hours.
What happens on Forkes Testserver when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 1 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does Forkes Testserver place in the wider field of Rust servers?
In the top 60% of all ranked servers, Forkes Testserver sits at #13,065 for player hours over the last seven days.
What does the population on Forkes Testserver look like?
Forkes Testserver is offline at the moment; the last time it was seen was 9 days 15 hours ago.
Tags
How should you read the tags on Forkes Testserver?
You'll see Forkes Testserver tagged with gmvanilla (Game mode): You play vanilla survival here; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Forkes Testserver?
These Rust Server Score lists count Forkes Testserver among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
Which rules does Forkes Testserver enforce, and what are its settings?
The name of Forkes Testserver gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
Forkes Testserver runs which map?
The game generates a procedural map for Forkes Testserver.
Connecting
How should you connect to Forkes Testserver?
To connect, start Rust, press F1, and type client.connect 84.134.57.199:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmvanilla,cs167781,ts8,^z,^y
Game
gmvanilla
Game modeYou play vanilla survival here.
mp2
Max playersThe server holds 2 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is Carbon.
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); momentum is the one to work on (F).