Vuky | Solo only | Weekly |Test server
Online 157.85.87.232:26294 checked 16m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. 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 0, 0 hours in.
Wipes
every wipe as a delivery, newest first-
Sat 3 Oct, 04:06 UTC 05:06 UK · 25d agoWipe delivered
- Peak
- 0
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Sun 13 Sep, 15:12 UTC 16:12 UK · 44d agoWipe delivered
- Peak
- 4
- Crowd
- halved by day 2
- Lasted
- 19.5 days
- Players before
- 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
The same kind of game, then region, group limit, rate and wipes.
- Rusty Moose |EU Mondays| 309 / 300
- Rustoria.co - EU Main 21 / 250
- Rusty Moose |EU Main| 18 / 250
- Rustoria.co - EU East Long 199 / 200
- Rustoria.co - EU East Medium 102 / 200
- Rustafied.com - EU Friday 28 / 100
Quick answers
From the figures on this page.
Player activity
What is the ranking of Vuky | Solo only | Weekly |Test server against other Rust servers?
A seven-day player-hours count places Vuky | Solo only | Weekly |Test server at #15,412: the top 69% of every ranked server.
What is the current population on Vuky | Solo only | Weekly |Test server?
The current count is 0 players on 50 slots for Vuky | Solo only | Weekly |Test server. The seven-day average for this server is 0 players.
Server rules
On what map does Vuky | Solo only | Weekly |Test server take place?
The game generates the procedural map on Vuky | Solo only | Weekly |Test server at size 3,500 with seed 3106. Identical size and seed give an identical map: view it on RustMaps from this page.
What settings and rules should you know for Vuky | Solo only | Weekly |Test server?
No gather rate appears in the name of Vuky | Solo only | Weekly |Test server. 8 players is the group limit, since the game's default applies. survival is the mode, gather and build and raid: the standard game. Raiding and PvP are both on. The server browser files it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.
Server details
What location does Vuky | Solo only | Weekly |Test server run from?
No region is published by Vuky | Solo only | Weekly |Test server. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. The address to connect to is 157.85.87.232:26294.
Does Vuky | Solo only | Weekly |Test server perform well?
Server fps over the last 48 hours averaged 114; the lowest was 104. The world held as many as 69,603 entities: buildings, deployables and the rest. 3,544 MB of memory was its top figure. Players feel a rising entity count and low fps as lag.
What is the uptime of Vuky | Solo only | Weekly |Test server, and is it online?
Vuky | Solo only | Weekly |Test server is up and online at the moment. About 1 hours ago is when it last restarted, judged by the uptime it gives. It was up 168 of 168 hours over the last 7 full days, 100% of the time. The first sighting of it by Rust Wipe Tracker came on 13 September 2026.
On what Rust version does Vuky | Solo only | Weekly |Test server operate?
The version on Vuky | Solo only | Weekly |Test server is Rust network protocol 2635 and build 168909, running on Linux. Steam keeps your game updated; it has to be on the same protocol to join.
Map resets
How does Vuky | Solo only | Weekly |Test server handle its wipe days?
The average busiest point of its recent wipes was 2 players. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Where that did not hold, it dropped below half by day 2.
On what schedule does Vuky | Solo only | Weekly |Test server reset its map?
To tell its rhythm we would need more of Vuky | Solo only | Weekly |Test server's wipes on record; there are too few yet. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. You are playing a world created 25 days 2 hours.
Tags and listings
On Rust Wipe Tracker, which lists and filters is Vuky | Solo only | Weekly |Test server part of?
You will find Vuky | Solo only | Weekly |Test server on the following Rust Wipe Tracker lists: Rust community servers, unmodded. On the server list, apply Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more and it appears.
What is the meaning of the server tags on Vuky | Solo only | Weekly |Test server?
Read off the game's server browser, the tags for Vuky | Solo only | Weekly |Test server are: gmrust (Game mode): Standard Rust survival is the game mode here; mp50 (Max players): Slot count: 50; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.
Connecting
What is the process to join Vuky | Solo only | Weekly |Test server?
Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 157.85.87.232:26294.