DWG RG-S3110Server sheetchecked 11m ago
yaga test
Online 212.193.10.54:28015 checked 11m ago
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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 14% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1,501, 2 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 15:19 UTC26d ago | 1,501 | – | running | 1 |
| Sat 3 Oct, 03:55 UTC26d ago | 1,501 | – | 0.5 days | 0 |
| Fri 2 Oct, 16:45 UTC27d ago | 1,501 | – | 0.5 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
Quick answers
Server data
What uptime is recorded for yaga test, and is it up?
Right now, yaga test is recorded as online. The uptime it reports puts the last restart at about 7 days 15 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 2 October 2026 is when Rust Graphs first saw it.
What does the recorded performance of yaga test show?
Average server fps over the last 48 hours is 86; the lowest was 44. Counted at its highest: 17,756 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 2,232 MB. A climbing entity count and low fps are the source of what players feel as lag.
What location is recorded for yaga test?
There is no region published by yaga test. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 212.193.10.54:28015 is its address.
On which Rust version is yaga test running?
The platform is Linux and the version is Rust network protocol 2634 and build 166652 on yaga test. The same protocol is required for joining, and Steam updates your game to it.
Counts
What player count is recorded on yaga test?
Current player count on yaga test: 1, of 2,000 slots. The seven-day mean is 1 players; the peak over the same period is 1. The 48-hour peak falls at 04:00 UTC, averaging 1 players.
Against other Rust servers, where is yaga test placed?
Player hours over seven days place yaga test at #3,110, within the top 14% of ranked servers.
Schedules
What happens on yaga test on the day of a wipe?
The recent wipes averaged a busiest count of 1,501 players. At 2 hours after the latest wipe the crowd was at its peak.
What wipe schedule has been recorded for yaga test?
No next wipe can be predicted for yaga test: its wipes fall at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 26 days 12 hours ago the current world was made.
Map and rules
Which settings does yaga test run, and what rules?
No gather rate is stated in the name of yaga test. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Plugins or settings change the game, and the browser lists it as Modded. Plugins run: Carbon. Anti-cheat: VAC, from Valve, is on.
Which map has yaga test loaded?
Seed 12345 and size 2,000 define the procedural map yaga test generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Filters
On Rust Graphs, which lists and filters contain yaga test?
These Rust Graphs lists include yaga test: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
On yaga test, what is meant by each tag?
The game's server browser reads these tags from yaga test: gmrust (Game mode): Standard survival, as Rust plays; mp2000 (Max players): Slots: 2,000; ts8 (Group limit): The team limit is 8, which is the game default; v2634 (Protocol): To join, your game must be on protocol 2634; cs166652 (Build): Build: 166652; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): Carbon is the plugin framework here. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Connect
By what method do you join yaga test?
Connect with client.connect 212.193.10.54:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
Server tags
Published as mp2000,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y
Game
gmrust
mp2000
ts8
v2634
cs166652
ptrak
$r?
Mods and access
^z
^y
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.