A.Server.Test
Online 202.36.95.176:23236 checked 11m ago
Server instruments
last reading Wed 17:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 162 · below 20 is lag, below 10 is badEntities
48 h range 44,366–48,516 · memory 2,590 MBUptime
17 h 4 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 22 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 29% of all ranked servers. Ranked on player hours over the last seven days.
World resets
a new world every few hours; none of these counts as a wipe| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 24 Oct, 22:10 UTC3d ago | – | – | – | 0 |
| Sat 24 Oct, 21:42 UTC3d ago | – | – | – | 0 |
| Sat 24 Oct, 20:48 UTC3d ago | – | – | – | 0 |
| Sat 24 Oct, 20:35 UTC4d ago | – | – | – | 0 |
| Sat 24 Oct, 19:19 UTC4d ago | – | – | – | 0 |
| Thu 22 Oct, 13:46 UTC6d ago | – | – | – | 1 |
| Thu 22 Oct, 13:03 UTC6d ago | 1 | held half | 2.3 days | 1 |
Similar servers
the same kind of game, then region, group limit, rate and wipes- 106/300
- 27/3300
- 1/300
- 0/50
- 2/40
- 1/300
Quick answers
from the figures on this pageWipe schedule
What wipe timing does A.Server.Test follow?
A new world is made every few hours by A.Server.Test, which keeps no wipe schedule; those resets are not wipes.
Tags
How should you read the tags on A.Server.Test?
Tags published by A.Server.Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): 40 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does A.Server.Test appear in Rust Metrics lists and filters?
On Rust Metrics, A.Server.Test sits in these lists: 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.
Player count
Where does A.Server.Test sit in the rankings?
Player hours over seven days put A.Server.Test at #6,411, in the top 29% of all ranked servers.
What player count does A.Server.Test carry?
0 of 40 slots are filled on A.Server.Test right now. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 15:00 UTC, averaging 1 players at that hour.
Server details
Which location does A.Server.Test run from?
No region comes from A.Server.Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 202.36.95.176:23236.
What Rust version is A.Server.Test on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by A.Server.Test. Matching protocol is required to join. Let Steam update your game.
What is the performance reading for A.Server.Test?
Over the last 48 hours the average was 209 server fps; the floor was 162. Reading: 48,516 entities at the highest. That covers buildings, deployables and everything else. Reading: 3,562 MB of memory at the highest. Expect lag when fps falls and entities climb.
Is A.Server.Test up, and how often does it stay up?
Reading: online. A.Server.Test answers right now. Reading: uptime. About 17 hours ago it restarted, on its own count. Reading: 100% uptime over the last 5 full days. It was up 120 of 120 hours. Check: first contact. Rust Metrics logged it on 22 October 2026.
Settings and map
How is A.Server.Test configured, and what rules are in force?
Reading the name gives no gather rate for A.Server.Test. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
What map is A.Server.Test on?
Check: map. Procedural, size 2,500, seed 45000, generated by the game on A.Server.Test. View it on RustMaps from this page: matching size and seed give an identical map. Its map carries the name Custom Map.
Join
How can you get onto A.Server.Test?
Press F1 in Rust and enter client.connect 202.36.95.176:23236. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.