测试123456789
Online 118.178.196.247:28015 checked 10m ago
Server instruments
last reading Fri 05:00 UTCPlayers now
100% full 7-day avg7-day peakServer fps
48 h low 110 · below 20 is lag, below 10 is badEntities
48 h range 70,174–77,576 · memory 2,205 MBUptime
2 h 14 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 25 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 21% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. 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, 1 hours in, with 1 in the queue.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 29 Oct, 13:34 UTC17h ago | – | – | running | 1 |
| Tue 27 Oct, 03:08 UTC3d ago | 1+1 queue | held half | 2.4 days | 0 |
| Mon 26 Oct, 03:43 UTC4d ago | 1 | – | 1 days | 1 |
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- 34/100
- 29/200
- 1/100
- 22/100
- 19/100
- 18/100
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on 测试123456789?
An average of 1 players came at the busiest on its recent wipes. 1 hours after the wipe the crowd peaked on the latest wipe, with 1 more in the queue. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.
When does 测试123456789 wipe?
No next wipe can be predicted for 测试123456789, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 17 hours ago the current world was made.
Lists and filters
Which tags does 测试123456789 carry, and what do they mean?
These are the tags 测试123456789 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does 测试123456789 appear in Rust Metrics lists and filters?
Rust Metrics lists featuring 测试123456789: Modded Rust servers, checked live. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Player count
What position does 测试123456789 hold among Rust servers?
Ranking for 测试123456789: #4,658 on seven-day player hours, top 21% of all ranked servers.
How full does 测试123456789 get?
Current headcount on 测试123456789: 1 players, 1 slots available. Check: players over seven days. Average 1, peak 1. Check: 48-hour peak. 10:00 UTC, 1 players on average.
Server details
What location is 测试123456789 hosted in?
The name of 测试123456789 points to Asia, though it publishes no region tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 118.178.196.247:28015.
What Rust version is 测试123456789 on?
Reading: 测试123456789, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for 测试123456789?
Check: fps. Average 159 server fps over the last 48 hours, low of 110. Within range. Reading: 77,576 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 2,406 MB. Expect lag when fps falls and entities climb.
Is 测试123456789 up, and how often does it stay up?
Reading: online. 测试123456789 answers right now. By its reported uptime, the last restart was roughly 2 hours ago. Reading: 91% uptime over the last 4 full days. It was up 87 of 96 hours. Check: first contact. Rust Metrics logged it on 25 October 2026.
Settings and map
How is 测试123456789 configured, and what rules are in force?
No gather rate appears in the name: 测试123456789. 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. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC off, Valve's system.
Which map is live on 测试123456789?
Check: map. Procedural, size 3,500, seed 1573025114, generated by the game on 测试123456789. View it on RustMaps from this page: matching size and seed give an identical map.
Join
How can you get onto 测试123456789?
To join: start Rust, press F1 and type client.connect 118.178.196.247:28015. Or press Launch Rust here and Steam opens the game and connects you. Reading: full. Expect to queue.