t8ezyq
Offline 37.214.64.42:28015 checked 42d ago
Server instruments
no direct query in 48 hoursPlayers now
25% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe 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
the same kind of game, then region, group limit, rate and wipes- 34/500
- 135/100
- 34/225
- 28/700
- 3/200
- 4/1000
Quick answers
from the figures on this pageReset cycle
How often does t8ezyq wipe, and when?
Its rhythm cannot be told from the wipes of t8ezyq on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 42 days 8 hours ago.
Tags
How should you read the tags on t8ezyq?
These are the tags t8ezyq publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp20 (Max players): 20 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163207 (Build): The server runs game build 163207; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show t8ezyq?
Rust Metrics lists featuring t8ezyq: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does t8ezyq hold among Rust servers?
Ranking for t8ezyq: #9,585 on seven-day player hours, top – of all ranked servers.
What is the population on t8ezyq?
Reading for t8ezyq: offline at this moment; last seen 42 days 6 hours ago.
Server
Where does t8ezyq sit?
Reading: location. t8ezyq gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 37.214.64.42:28015.
What Rust version is t8ezyq on?
Rust network protocol 2633 and build 163207 on Windows is the build t8ezyq runs. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on t8ezyq, and is it online?
Reading: offline. t8ezyq last answered 42 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 16 September 2026.
Settings and map
How is t8ezyq configured, and what rules are in force?
No gather rate appears in the name: t8ezyq. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is t8ezyq on?
Procedural map on t8ezyq, made by the game's generator.
How to join
How can you get onto t8ezyq?
Press F1 in Rust and enter client.connect 37.214.64.42:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.