RPTEST
Offline 94.29.35.120:28116 checked 3d 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 bestTop 69% of all ranked servers. 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- 338/375
- 441/475
- 979/1000
- 46/100
- 985/1000
- 64/250
Quick answers
from the figures on this pageReset cycle
What wipe timing does RPTEST follow?
To tell the rhythm of RPTEST, 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 3 days 23 hours ago.
Lists and filters
Which tags does RPTEST carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from RPTEST. 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 RPTEST?
Rust Metrics lists featuring RPTEST: 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; Last wipe: In the last week.
Occupancy
What position does RPTEST hold among Rust servers?
Ranking for RPTEST: #15,310 on seven-day player hours, top 69% of all ranked servers.
How full does RPTEST get?
Reading for RPTEST: offline at this moment; last seen 3 days 23 hours ago. Seven-day reading: 0 players on average.
Server
Which location does RPTEST run from?
No region comes from RPTEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 94.29.35.120:28116.
What Rust version is RPTEST on?
Reading: RPTEST, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.
Is RPTEST up, and how often does it stay up?
RPTEST reports offline. The last reading came 3 days 23 hours ago. Reading: 0% uptime over the last 3 full days. It was up 0 of 72 hours. The first sighting on Rust Metrics was 25 October 2026.
Settings and map
What settings and rules apply on RPTEST?
Reading the name gives no gather rate for RPTEST. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.
How to join
What do you do to join RPTEST?
Check: join. Open Rust, press F1, then enter client.connect 94.29.35.120:28116. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.