MY TEST SERVER | Default
Online 120.220.76.192:13231 checked 9m ago
Server instruments
last reading Wed 03:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 56 · below 20 is lag, below 10 is badEntities
48 h range 59,365–62,919 · memory 2,733 MBUptime
1 days 10 hours 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 28% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. 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 1, 15 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 22 Oct, 14:05 UTC5d ago | 1 | – | running | 0 |
| Thu 1 Oct, 17:56 UTC FW26d ago | 1 | halved by day 1 | 20.8 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- 42/500
- 134/100
- 53/225
- 23/700
- 4/200
- 7/1000
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on MY TEST SERVER | Default?
At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 15 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 1 when it didn't.
What wipe timing does MY TEST SERVER | Default follow?
The rhythm of MY TEST SERVER | Default's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 5 days 14 hours ago the current world was made.
Tag meanings
How should you read the tags on MY TEST SERVER | Default?
Tags published by MY TEST SERVER | Default, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp3 (Max players): Slots: 3; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show MY TEST SERVER | Default?
These Rust Metrics lists carry MY TEST SERVER | Default: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Population
What position does MY TEST SERVER | Default hold among Rust servers?
Player hours over seven days put MY TEST SERVER | Default at #6,200, in the top 28% of all ranked servers.
What is the population on MY TEST SERVER | Default?
0 of 3 slots are filled on MY TEST SERVER | Default right now. Seven-day check: 0 players on average. Peak reading: 1. Average at the busiest hour was 1 players, at 06:00 UTC over the last 48 hours.
Operator and location
Which location does MY TEST SERVER | Default run from?
No region comes from MY TEST SERVER | Default. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 120.220.76.192:13231.
What Rust version is MY TEST SERVER | Default on?
Rust network protocol 2635 and build 168909 on Windows is the build MY TEST SERVER | Default runs. Matching protocol is required to join. Let Steam update your game.
How does MY TEST SERVER | Default perform?
Reading: 108 server fps on average across the last 48 hours. It never dropped below 56. Peak entity count: 62,919. Buildings, deployables and all else included. Check: memory. Peak use was 2,907 MB. Lag, as players feel it, is low fps plus a climbing entity count.
How reliable is MY TEST SERVER | Default, and is it online now?
Reading: online. MY TEST SERVER | Default answers right now. Check: restart. The uptime it reports puts the last restart about 34 hours ago. Reading: 68% uptime over the last 7 full days. It was up 115 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Rules and settings
How is MY TEST SERVER | Default configured, and what rules are in force?
Check: gather rate. The name MY TEST SERVER | Default does not state one. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
Which map is live on MY TEST SERVER | Default?
Check: map. Procedural, size 4,096, seed 1337, generated by the game on MY TEST SERVER | Default. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Read the map name: Custom Map.
Join
How can you get onto MY TEST SERVER | Default?
Press F1 in Rust and enter client.connect 120.220.76.192:13231. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.