LOCAL UPDATE TEST
Offline 144.31.239.85:29015 checked 5d 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 72% 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
- 193/ 225
- 383/ 425
- 237/ 250
- 146/ 200
- 147/ 200
- 197/ 250
Quick answers
Tags and filters
Where does LOCAL UPDATE TEST appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include LOCAL UPDATE TEST: Rust community servers, going deep. You can find it on the server list by these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
How should you read the tags on LOCAL UPDATE TEST?
LOCAL UPDATE TEST's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): The slot count is 10; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167584 (Build): It's on build 167584; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
What's the location of LOCAL UPDATE TEST?
There is no published region for LOCAL UPDATE TEST. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 144.31.239.85:29015.
How reliable is LOCAL UPDATE TEST?
Right now LOCAL UPDATE TEST is offline, having last been seen 5 days 13 hours ago. Over the past full 5 days it stayed up for 0 of 120 hours, or 0%. The first sighting by Rust Going Deep was on 12 October 2026.
What Rust version is LOCAL UPDATE TEST on?
On Windows, LOCAL UPDATE TEST runs Rust network protocol 2634 and build 167584. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
How often does LOCAL UPDATE TEST wipe?
LOCAL UPDATE TEST's rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 5 days 13 hours is how long ago this world came into being.
Settings and map
Which rules and settings is LOCAL UPDATE TEST running?
No gather rate appears in the name of LOCAL UPDATE TEST. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser lists it under Community, making it a community server. VAC, Valve's anti-cheat, is enabled.
What's the map on LOCAL UPDATE TEST?
LOCAL UPDATE TEST uses a game-generated procedural map.
Player stats
How many players are on LOCAL UPDATE TEST?
LOCAL UPDATE TEST was last seen 5 days 13 hours ago and is offline as you read this. The seven-day average for players here is 0.
What's LOCAL UPDATE TEST's rank among Rust servers?
Over the last seven days, LOCAL UPDATE TEST is #15,853 by player hours, among the top 72% of all ranked servers.
How to join
What's the process to join LOCAL UPDATE TEST?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 144.31.239.85:29015.