TEST SERVER
Online EU 185.139.70.176:28015 checked 8m ago
Server instruments
last reading Thu 15:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 160 · below 20 is lag, below 10 is badEntities
48 h range 17,183–20,745 · memory 1,581 MBUptime
13 h 15 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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers, top 87% in EU. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The 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- 460/475
- 254/275
- 121/350
- 163/400
- 92/125
- 160/300
Quick answers
from the figures on this pageReset cycle
How often does TEST SERVER wipe, and when?
From the force wipe, the next wipe of TEST SERVER is an estimate. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 27 days 22 hours ago the current world was made. A monthly wipe schedule is published in its tags.
Tags
Which tags does TEST SERVER carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): The server runs game build 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^y (Carbon): Carbon handles the plugins here; EU (Europe): The server browser files it under Europe from TEST SERVER. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which operator is behind TEST SERVER?
Most likely the same operator runs both: TEST SERVER publishes a notfriendly.ru hostname, and 1 other server we track does the same.
Which lists and filters on Rust Metrics show TEST SERVER?
Rust Metrics lists featuring TEST SERVER: EU Rust servers, checked, Rust community servers: live readings and Vanilla Rust servers, live. Reading: server list filters. It comes up under Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m, Vanilla ^v and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Occupancy
What position does TEST SERVER hold among Rust servers?
Top 69% of all ranked servers: TEST SERVER takes #15,341 on seven-day player hours and #2,549 in Europe.
How full does TEST SERVER get?
Current headcount on TEST SERVER: 0 players, 100 slots available. Check: player average. 0 over the last seven days.
Operator and location
Which location does TEST SERVER run from?
Reading: location. The EU tag puts TEST SERVER in Europe. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 185.139.70.176:28015.
What Rust version is TEST SERVER on?
Reading: TEST SERVER, Rust network protocol 2634 and build 166494, Linux. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on TEST SERVER within range?
Check: fps. Average 219 server fps over the last 48 hours, low of 160. Within range. Reading: 20,745 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 1,819 MB. Expect lag when fps falls and entities climb.
Is TEST SERVER up, and how often does it stay up?
Check: connection. TEST SERVER is online at this moment. Check: restart. The uptime it reports puts the last restart about 13 hours ago. Uptime for the last 7 full days: 141 of 168 hours, or 84%. The first sighting on Rust Metrics was 4 October 2026.
Settings and map
How is TEST SERVER configured, and what rules are in force?
Reading the name gives no gather rate for TEST SERVER. 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. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: plugins. It runs Carbon of them. The server calls itself vanilla, with this meaning: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Check: anti-cheat. VAC, Valve's system, is on.
What map is TEST SERVER on?
Check: map. Procedural, size 2,000, seed 48142459, generated by the game on TEST SERVER. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
How to join
How can you get onto TEST SERVER?
Check: join. Open Rust, press F1, then enter client.connect 185.139.70.176:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.