LOCAL TEST SERVER
Offline 193.138.245.205:28015 checked 21d 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 61% 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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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
Quick answers
Tags and search
Where does LOCAL TEST SERVER appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry LOCAL TEST SERVER are: Rust community servers, going deep and Go deep on PvE servers. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
How should you read the tags on LOCAL TEST SERVER?
gmrust (Game mode): This is the standard Rust survival experience; mp4 (Max players): It holds 4 players; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs165217 (Build): This server runs build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^p (PvE): No PvP here: the danger comes from the environment — that is the tag list LOCAL TEST SERVER puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What location is LOCAL TEST SERVER in?
There is no published region for LOCAL TEST SERVER. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. To connect, use 193.138.245.205:28015.
How reliable is LOCAL TEST SERVER?
The server LOCAL TEST SERVER is not reachable at the moment; the last sighting was 21 days 14 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. Rust Going Deep has had it on record since 26 September 2026.
What is the Rust version for LOCAL TEST SERVER?
On Windows, LOCAL TEST SERVER runs Rust network protocol 2633 and build 165217. The protocol must match to join; Steam will update your game.
Wipe schedule
When does LOCAL TEST SERVER wipe?
Too few wipes are on record for LOCAL TEST SERVER to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 24 days 21 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is LOCAL TEST SERVER running?
Its name does not state a gather rate for LOCAL TEST SERVER. The group limit is the game's default of 8 players. It runs pve, no fighting other players. The server browser lists it under Community, making it a community server. VAC, Valve's anti-cheat, is disabled.
Which map is active on LOCAL TEST SERVER?
The map on LOCAL TEST SERVER is procedural, made by the game.
Population
Is LOCAL TEST SERVER busy?
The last sighting of LOCAL TEST SERVER was 21 days 14 hours ago; it is offline right now.
What position does LOCAL TEST SERVER hold in the server rankings?
For player hours in the last seven days, LOCAL TEST SERVER ranks #14,351, within the top 61% of ranked servers.
Join info
What's the process to join LOCAL TEST SERVER?
To join, open Rust, hit F1, and enter client.connect 193.138.245.205:28015. Or click Launch Rust on this page to open the game through Steam and connect.