Server profile
Local Plugin Test (not public)
Offline, with 0 of 4 players on; ranked #14,597 of every public Rust server, the top 66%. It last wiped 19d ago.
Offline 208.188.186.148:28015 checked 10h 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. 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 66% 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 1, 1 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 19 Oct, 06:31 UTC10d ago | 1 | – | running | 0 |
| Fri 9 Oct, 12:56 UTC19d ago | 1 | halved by day 1 | 9.7 days | 0 |
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 cycle
On Local Plugin Test (not public), what happens on wipe day?
The average busiest point of its recent wipes was 1 players. 1 hours after the latest wipe, the crowd peaked. Half the peak held until the next wipe in 0% of its recent wipes. In the other cases, it dropped below half by day 1.
On what schedule does Local Plugin Test (not public) wipe?
Its rhythm cannot be read yet: Local Plugin Test (not public) has too few wipes on record. The monthly force wipe comes to all Rust servers next on Thursday 5 November at 19:00 UTC. 19 days 22 hours have passed since its current world was created.
Server
Which Rust version is Local Plugin Test (not public) on?
Rust network protocol 2635 and build 168909 on Windows is what Local Plugin Test (not public) runs. You can only join if your game is on the same protocol; Steam handles that update.
How reliable is Local Plugin Test (not public), and is it up at the moment?
Local Plugin Test (not public) is offline at the moment; the last time it was seen was 10 hours ago. It spent 4 of the last 7 full days' 168 hours up, 2% of the time. On 30 September 2026 is when Rust Insights first saw it.
Where does Local Plugin Test (not public) run from?
A region is not published by Local Plugin Test (not public). Rust Insights reports the location a server declares, not the physical place of the machine. You can reach it at 208.188.186.148:28015.
Server tags
How should you read the tags listed for Local Plugin Test (not public)?
The tags gmrust (Game mode): Survival as standard Rust plays; mp4 (Max players): 4 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): Build 168909 is what it runs; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it is filed under Modded are what Local Plugin Test (not public) 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.
Which Rust Insights filters and lists feature Local Plugin Test (not public)?
Local Plugin Test (not public) 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
How many players are on Local Plugin Test (not public) right now, and how does that number move?
Local Plugin Test (not public) was last seen 10 hours ago and is offline right now. The seven-day average is 0 players, and the highest point in that week was 1. Look at the last 48 hours and the peak hour is 21:00 UTC, at 0 players on average.
How does Local Plugin Test (not public) compare with other Rust servers in the ranking?
Player hours over seven days put Local Plugin Test (not public) at #14,597, within the top 66% of the ranked field.
Rules and settings
How is Local Plugin Test (not public) configured, and what rules apply?
No gather rate appears in the name of Local Plugin Test (not public). 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. It is a Modded entry: plugins or settings modify the game. Oxide is the plugin count it runs. Anti-cheat: VAC, from Valve, is on.
What is the map on Local Plugin Test (not public)?
A procedural map, generated by the game, is what Local Plugin Test (not public) runs.
Join
How do you connect to Local Plugin Test (not public)?
To connect, start Rust and enter client.connect 208.188.186.148:28015 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.