cRUSTest
Offline 179.107.251.157:28015 checked 42d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer 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 bestWipe 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- 346/400
- 459/500
- 983/1000
- 45/100
- 992/1000
- 43/250
Quick answers
from the figures on this pageReset cycle
When does cRUSTest wipe?
Its rhythm cannot be told from the wipes of cRUSTest on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 42 days 19 hours ago.
Lists and filters
How should you read the tags on cRUSTest?
Tags published by cRUSTest, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Game build reading: 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does cRUSTest appear in Rust Metrics lists and filters?
On Rust Metrics, cRUSTest sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
What position does cRUSTest hold among Rust servers?
Ranking for cRUSTest: #15,481 on seven-day player hours, top – of all ranked servers.
How full does cRUSTest get?
cRUSTest is not responding; status offline, last seen 42 days 5 hours ago.
Server
What location is cRUSTest hosted in?
No region tag on cRUSTest. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 179.107.251.157:28015.
What Rust version is cRUSTest on?
Rust network protocol 2633 and build 164530 on Windows is the build cRUSTest runs. Matching protocol is required to join. Let Steam update your game.
What is the uptime on cRUSTest, and is it online?
Check: connection. cRUSTest is offline at this moment. Last contact was 42 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 16 September 2026.
Rules and settings
What settings and rules apply on cRUSTest?
Reading the name gives no gather rate for cRUSTest. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
What map is cRUSTest on?
Procedural map on cRUSTest, made by the game's generator.
How to join
How can you get onto cRUSTest?
Press F1 in Rust and enter client.connect 179.107.251.157:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.