TESTING SERVER
Offline 115.133.77.132:28025 checked 19d 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 71% 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 TESTING SERVER appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include TESTING SERVER: 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 TESTING SERVER?
The server browser shows these tags for TESTING SERVER: gmvanilla (Game mode): The mode is vanilla survival; mp2 (Max players): It holds 2 players; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs165217 (Build): It's on build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^p (PvE): It's player versus environment, so the world poses the risk, not other players. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What's the location of TESTING SERVER?
TESTING SERVER 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. To connect, use 115.133.77.132:28025.
What's the uptime like for TESTING SERVER?
TESTING SERVER is down at the moment; it was last up 19 days 17 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 28 September 2026 is when Rust Going Deep first saw it.
What Rust version is TESTING SERVER on?
On Windows, TESTING SERVER runs Rust network protocol 2633 and build 165217. The protocol must match to join; Steam will update your game.
Wipe schedule
When does TESTING SERVER wipe?
TESTING SERVER's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 19 days 17 hours ago.
Rules and settings
What settings are in place on TESTING SERVER?
No gather rate appears in the name of TESTING SERVER. The group limit is the game's default of 8 players. pve is the game mode, no fighting other players. Community is where the server browser puts it, as a community server. VAC is on: Valve's anti-cheat is active.
What's the map on TESTING SERVER?
The map on TESTING SERVER is procedural, made by the game.
Population
How many players are on TESTING SERVER?
TESTING SERVER was last seen 19 days 17 hours ago and is offline as you read this.
What position does TESTING SERVER hold in the server rankings?
Over the last seven days, TESTING SERVER is #16,970 by player hours, among the top 71% of all ranked servers.
Getting in
How do you get into TESTING SERVER?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 115.133.77.132:28025.