Local Builder Test
Offline 31.30.165.49:28015 checked 31d 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 bestWipe 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
- 19/ 101
- 2/ 25
- 52/ 999
- 66/ 999
- 74/ 150
- 111/ 150
Quick answers
Tags and listings
Where does Local Builder Test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Local Builder Test are: Rust build and creative servers and Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Local Builder Test?
gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): There are 2 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs163794 (Build): The build number is 163794; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty — that is the tag list Local Builder Test 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 details
What's the location of Local Builder Test?
Local Builder Test does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 31.30.165.49:28015.
How reliable is Local Builder Test?
The server Local Builder Test is not reachable at the moment; the last sighting was 31 days 16 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 15 September 2026.
What Rust version is Local Builder Test on?
Rust network protocol 2633 and build 163794 is what Local Builder Test runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
How often does Local Builder Test wipe?
Too few wipes are on record for Local Builder Test to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. The world you are on now was created 32 days 8 hours.
Rules and settings
Which rules and settings is Local Builder Test running?
No gather rate appears in the name of Local Builder Test. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. It sits under Community in the server browser: a community server. VAC, Valve's anti-cheat, is disabled.
What's the map on Local Builder Test?
Local Builder Test uses a game-generated procedural map.
Population
How many players are on Local Builder Test?
The last sighting of Local Builder Test was 31 days 16 hours ago; it is offline right now.
What's Local Builder Test's rank among Rust servers?
For player hours in the last seven days, Local Builder Test ranks #14,206, within the top – of ranked servers.
Getting in
What's the process to join Local Builder Test?
Open Rust and press F1, then type client.connect 31.30.165.49:28015. Alternatively, click Launch Rust on this page to join via Steam.