Station XX-12699 · no signal
ChainLinkHosting Rust validation
Offline 116.91.213.117:28015 checked 2d ago
- Players now
- 1/ 4
- 25% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #12,699
- top 57%
- Last wipe
- 12d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 4 slots
- Motion · 24 h
- M –not enough readings
Players
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 bestTop 57% of all ranked servers. Ranked on player hours over the last seven days.
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on ChainLinkHosting Rust validation?
A procedural map runs on ChainLinkHosting Rust validation, generated by the game.
Which settings and rules apply on ChainLinkHosting Rust validation?
The name of ChainLinkHosting Rust validation gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on ChainLinkHosting Rust validation right now?
ChainLinkHosting Rust validation is not responding at this moment and is offline, last seen 2 days 15 hours ago. Across seven days this server recorded an average of 1 players and a peak of 1.
How does ChainLinkHosting Rust validation rank against other Rust servers?
The last seven days of player hours place ChainLinkHosting Rust validation at #12,699, in the top 57% of all ranked servers.
Operator and location
How reliably does ChainLinkHosting Rust validation stay online?
As recorded now, ChainLinkHosting Rust validation is not reachable, the last contact having been 2 days 15 hours ago. Of the 24 hours in the last 1 full day, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 26 October 2026.
Which region does ChainLinkHosting Rust validation run from?
No region is published by ChainLinkHosting Rust validation. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 116.91.213.117:28015.
Which Rust version is ChainLinkHosting Rust validation running?
ChainLinkHosting Rust validation is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
How often does ChainLinkHosting Rust validation wipe, and on which days?
Too few wipes of ChainLinkHosting Rust validation are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 12 days 18 hours.
Tags
What do the server tags on ChainLinkHosting Rust validation mean?
These are the tags ChainLinkHosting Rust validation publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp4 (Max players): 4 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does ChainLinkHosting Rust validation appear?
These Rust Server Trends lists include ChainLinkHosting Rust validation: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connecting
How do you connect to ChainLinkHosting Rust validation?
Enter client.connect 116.91.213.117:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.