Live coverage · Rust server
Offline trident local test is not on the server list right now. The figures below are from when it was last seen, 1d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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.
Too few wipes are recorded for trident local test to establish a pattern. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. The world you are playing on was built 30 hours.
On Rust Live Stats, trident local test is listed under Live Rust community servers. These filters on the server list bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
The server browser reads gmrust (Game mode): Survival here follows standard Rust; mp10 (Max players): The slot count is 10; ts8 (Group limit): Team cap: 8, which is the game default; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code, which trident local test publishes. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
trident local test is not online at the moment, having last been seen 29 hours ago. Averaged over seven days: 0 players.
Ranked by seven-day player hours, trident local test is #15,351, placing it in the top 69% of ranked servers.
Nothing in the name of trident local test states a gather rate. Eight players per group, which is the game's default. It runs survival, the standard game: gather, build, raid. Raiding and player combat are both permitted. You find it under Community in the server browser. VAC is enabled: Valve's anti-cheat.
trident local test uses a procedural map, which the game generates.
Nothing on trident local test states a region. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 146.70.134.32:28015.
Rust network protocol 2635 and build 168909 on Windows is what trident local test runs. Steam updates it for you, but your game needs the same protocol to join.
At the time of this update, trident local test is down, last seen 29 hours ago. 0 of 24 hours were online in the last 1 full day, giving 0% uptime. Rust Live Stats has tracked it since 27 October 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 146.70.134.32:28015.