Server profile
Wujasowo test
Online, with 0 of 50 players on; ranked #15,349 of every public Rust server, the top 69%. It last wiped 25d ago.
Online 147.93.160.205:28615 checked 12m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 69% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
Too few wipes seen yet.
Not 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 wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 12:34 UTC25d ago | 0 | – | running | 1 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe schedule
On Wujasowo test, what happens on wipe day?
Recent wipes peaked at 0 players on average. 0 hours into the latest wipe, the crowd on the server reached its peak.
On what schedule does Wujasowo test wipe?
Its rhythm cannot be read yet: Wujasowo test has too few wipes on record. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. This world dates from 25 days 15 hours ago.
Server details
Does Wujasowo test hold a steady frame rate?
Server fps averaged 46 over 48 hours; the lowest reading was 14. Buildings, deployables and the rest took the entity count as high as 16,752. Memory use peaked at 1,519 MB. A climbing entity count and low fps are what players experience as lag.
On what version does Wujasowo test currently run?
The Rust build is network protocol 2635 and build 168909, running on Windows, for Wujasowo test. Joining needs your game on the same protocol, which Steam updates for you.
Has Wujasowo test stayed online, and is it up now?
At the time of this check Wujasowo test is online. The uptime it reports puts the last restart at about 6 days 7 hours ago. It spent 167 of the last 7 full days' 168 hours up, 99% of the time. On 2 October 2026 is when Rust Insights first saw it.
In which location does Wujasowo test sit?
A region is not published by Wujasowo test. Rust Insights reports the location a server declares, not the physical place of the machine. You can reach it at 147.93.160.205:28615.
Lists and tags
How should you read the tags listed for Wujasowo test?
The tags gmvanilla (Game mode): Vanilla survival is the mode; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams cap at 8; v2635 (Protocol): Your game must run the same version to join: the protocol is 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings alter the game, so it is filed under Modded are what Wujasowo test publishes, and the server browser in the game reads them. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
Where does Wujasowo test turn up among the Rust Insights lists and filters?
Wujasowo test appears among the following Rust Insights lists: Modded Rust servers, explained. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population history
What does the population of Wujasowo test look like?
Of its 50 slots, Wujasowo test currently has 0 filled. Its average over seven days comes to 0 players.
Where does Wujasowo test sit in the rankings?
Player hours over seven days put Wujasowo test at #15,349, within the top 69% of the ranked field.
Rules and settings
How is Wujasowo test configured, and what rules apply?
No gather rate appears in the name of Wujasowo test. Groups can reach 8 players, which is the default in the game. You get survival as the game mode, the standard game: gather, build, raid. Players may raid and fight one another. The server browser lists it under Modded: plugins or settings alter the game. It runs plugins, Oxide of them. VAC is on: Valve's anti-cheat is active.
Which map is live on Wujasowo test?
Wujasowo test runs a procedural map of size 2,000 with seed 2147483647, generated by the game. The same size and seed produce the same map, so from this page you can look at it on RustMaps.
Connecting
How do you connect to Wujasowo test?
Type client.connect 147.93.160.205:28615 into the console, which you open with F1 in Rust. The Launch Rust button on this page does the same job by opening Rust through Steam.