Test server
Online 191.44.68.101:40121 checked 8m ago
Server instruments
last reading Thu 09:00 UTCPlayers now
1% full 7-day avg7-day peakServer fps
48 h low 39 · below 20 is lag, below 10 is badEntities
48 h range 18,442–63,882 · memory 2,570 MBUptime
8 h 26 min since its last restart, at the last readingPlayers
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, measured since 20 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 42% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 28 Oct, 19:59 UTC14h ago | – | – | running | 0 |
| Fri 23 Oct, 17:11 UTC5d ago | 0 | – | 5.1 days | 0 |
| Tue 20 Oct, 14:16 UTC8d ago | 2 | held half | 3.1 days | 0 |
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- 143/500
- 122/100
- 186/225
- 78/700
- 10/200
- 20/1000
Quick answers
from the figures on this pageReset cycle
What happens on Test server when wipe day comes?
An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. Until the next wipe, the crowd stayed above half that peak in 100% of its recent wipes.
What wipe timing does Test server follow?
There is no next wipe to predict: Test server wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 14 hours ago.
Lists and filters
How should you read the tags on Test server?
Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server; rustmaps (Custom tag): Owner or plugin definition: this tag is not a standard Rust one from Test server. 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 Test server?
On Rust Metrics, Test server sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Player count
Where does Test server sit in the rankings?
Player hours over seven days put Test server at #9,350, in the top 42% of all ranked servers.
How full does Test server get?
Current headcount on Test server: 1 players, 100 slots available. Seven-day check: 0 players on average. Peak reading: 1. The last 48 hours peaked at 20:00 UTC, averaging 1 players at that hour.
Server
Where does Test server sit?
Reading: location. Test server gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 191.44.68.101:40121.
What Rust version is Test server on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by Test server. Matching protocol is required to join. Let Steam update your game.
How does Test server perform?
Check: fps. Average 51 server fps over the last 48 hours, low of 39. Within range. Check: entities. The peak was 63,882, counting buildings, deployables and the rest of the world. Reading: 2,575 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on Test server, and is it online?
Reading: online. Test server answers right now. Reading: uptime. About 8 hours ago it restarted, on its own count. Uptime for the last 7 full days: 58 of 168 hours, or 35%. The first sighting on Rust Metrics was 20 October 2026.
Settings and map
How is Test server configured, and what rules are in force?
No gather rate appears in the name: Test server. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Vanilla is the label it uses: rates, kits and rules are exactly as Facepunch ships them. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Test server?
Size 3,500, custom map, on Test server. The file is published and downloadable here.
How to join
How can you get onto Test server?
To join: start Rust, press F1 and type client.connect 191.44.68.101:40121. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://verisunucu.net.