Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
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
No region is published for t8ezyq. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 37.214.64.42:28015.
How reliable is t8ezyq, and is it up?
The server is down: t8ezyq is offline now, with the last sighting 42 days ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 16 September 2026, Rust Server Score saw it for the first time.
Which Rust version is t8ezyq running?
The server t8ezyq is on Rust network protocol 2633 and build 163207 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does t8ezyq reset?
t8ezyq has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 42 days 1 hours.
Player numbers
Where does t8ezyq sit among Rust servers?
In the top – of all ranked servers, t8ezyq sits at #9,585 for player hours over the last seven days.
Is t8ezyq a busy server?
It has been 42 days since t8ezyq was last seen, and it is offline right now.
Tags and filters
How should you read the tags on t8ezyq?
gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): Its slot count is 20; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163207 (Build): Build number: 163207; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags t8ezyq publishes, and the game's server browser reads them. 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 t8ezyq?
These Rust Server Score lists count t8ezyq among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which rules does t8ezyq enforce, and what are its settings?
The name of t8ezyq gives no gather rate. The group limit stays at the game's default of 8 players. 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. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
t8ezyq runs which map?
A procedural map, generated by the game, is what t8ezyq runs.
Getting in
What is the way to join t8ezyq?
Enter client.connect 37.214.64.42:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max playersIts slot count is 20.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163207
BuildBuild number: 163207.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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.
Not enough figures yet to write a report. Check back after a few days on the list.