Working its way up from the back of the class: #15,986 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
53/ 100
D
Moving up: up 853 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.
No daily history yet.
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. 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 Monday 2 November, 00:01 UTC, in 3d 23h.
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
EU · groups of 300+ · 2x · weekly · 129 on average
11 / 100
Quick answers
from the figures on this page
Server facts
In what location does FORGE | CORE 2x Trio | LOCAL TEST sit?
No region is published for FORGE | CORE 2x Trio | LOCAL TEST. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 45.228.67.134:28115 is the address to use.
Is FORGE | CORE 2x Trio | LOCAL TEST up, and how steady is its uptime?
The server is down: FORGE | CORE 2x Trio | LOCAL TEST is offline now, with the last sighting 22 days 4 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 6 October 2026.
Which Rust version is FORGE | CORE 2x Trio | LOCAL TEST running?
You will find FORGE | CORE 2x Trio | LOCAL TEST on Rust network protocol 2634 and build 166652, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does FORGE | CORE 2x Trio | LOCAL TEST wipe, and how often?
The next wipe on FORGE | CORE 2x Trio | LOCAL TEST is a projection from weekly: 7 days after its last wipe. Monday 2 November at 00:01 UTC is the date set for its next wipe. 24 days have passed since this world was made. The tags carry a weekly wipe schedule.
Population
What position does FORGE | CORE 2x Trio | LOCAL TEST hold in the rankings?
In the top 71% of all ranked servers, FORGE | CORE 2x Trio | LOCAL TEST sits at #15,986 for player hours over the last seven days.
How many players does FORGE | CORE 2x Trio | LOCAL TEST usually have?
FORGE | CORE 2x Trio | LOCAL TEST is offline at the moment; the last time it was seen was 22 days 4 hours ago.
Tags and filters
What do FORGE | CORE 2x Trio | LOCAL TEST's tags stand for?
The game's browser takes its cue from the tags FORGE | CORE 2x Trio | LOCAL TEST has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^w (Weekly): Wipes come once a week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature FORGE | CORE 2x Trio | LOCAL TEST?
These Rust Server Score lists count FORGE | CORE 2x Trio | LOCAL TEST among them: 2x Rust servers, graded 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: 5 or more; Wipe schedule: Weekly; Gather rate: 2x.
Map and rules
What settings and rules apply on FORGE | CORE 2x Trio | LOCAL TEST?
The name of FORGE | CORE 2x Trio | LOCAL TEST points to a 2x gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
FORGE | CORE 2x Trio | LOCAL TEST runs which map?
The game generates a procedural map for FORGE | CORE 2x Trio | LOCAL TEST.
How to join
What is the way to join FORGE | CORE 2x Trio | LOCAL TEST?
To connect, start Rust, press F1, and type client.connect 45.228.67.134:28115. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,^w,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyWipes come once a week.
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); standing is the one to work on (F).