TestServer
Offline 49.76.133.31:10241 checked 5h ago
Server instruments
no direct query in 48 hoursPlayers now
1% full 7-day avg7-day peakServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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, and #575 of the quad servers (top 70%). 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- 0/300
- 8/60
- 9/99
- 4/100
- 6/200
- 2/101
Quick answers
from the figures on this pageReset cycle
When does TestServer wipe?
To tell the rhythm of TestServer, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 25 days 14 hours ago.
Lists and filters
How should you read the tags on TestServer?
These are the tags TestServer publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts4 (Group limit): You may team up with at most 4; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show TestServer?
These Rust Metrics lists carry TestServer: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Quad.
Occupancy
What position does TestServer hold among Rust servers?
Player hours over seven days put TestServer at #13,494, in the top 61% of all ranked servers. Among servers in quad, it stands at #575.
What is the population on TestServer?
TestServer is not responding; status offline, last seen 5 hours ago. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 14:00 UTC, 1 players on average.
Server details
Where does TestServer sit?
Reading: location. TestServer gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 49.76.133.31:10241.
What Rust version is TestServer on?
Reading: TestServer, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.
Is TestServer up, and how often does it stay up?
Reading: offline. TestServer last answered 5 hours ago. Reading: first seen 27 October 2026, recorded by Rust Metrics.
Settings and map
What rules does TestServer enforce, and what are its settings?
No gather rate appears in the name: TestServer. Check: group limit. 4 players, under the name quad. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
Join
How can you get onto TestServer?
Press F1 in Rust and enter client.connect 49.76.133.31:10241. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.