An entry in the registerNo. 4,804
测试123456789
Online 118.178.196.247:28015 checked 11m ago
测试123456789 is a Rust server. At the last count it had 1 players of a possible 1; over the past week it averaged 1, with a peak of 1. It stands at No. 4,804 of the ranked servers, the top 22%. It last wiped 4h ago. Its own tags class it as modded, oxide.
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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.
§ 3Standingthe rank, daily · 1 is best
Top 22% of all ranked servers. Ranked on player hours over the last seven days.
§ 4The wipe scheduleno rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
between real wipes
of its recent wipes
players, last three wipes
of its cycles kept half the crowd
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.
§ 5The record of wipesnewest first
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 29 Oct, 13:34 UTC4h ago | – | – | running | 1 |
| Tue 27 Oct, 03:08 UTC2d ago | 1+1 queue | held half | 2.4 days | 0 |
| Mon 26 Oct, 03:43 UTC3d 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.
§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes
- 1 QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造33/100 EA · groups of 20+ · weekly · 25 on average
- 2 【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐36/200 EA · groups of 8+ · weekly · 21 on average
- 3 ［JP］初心者PVPサーバー｜RaidTime・ Events2/100 EA · groups of 10+ · biweekly · 15 on average
- 4 [守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新18/100 EA · no group limit · 12 on average
- 5 [霸道]10000000倍-10.29日-萌新首选-稳定长久18/100 EA · no group limit · 11 on average
- 6 #10-[搞就完了]10倍/10.29新档/无权/萌新首选20/100 EA · no group limit · 11 on average
§ 7Questions answeredfrom the figures in this entry
Server details
On which Rust version does 测试123456789 operate?
Rust network protocol 2635 and build 168909 on Windows is what 测试123456789 runs. The protocol must match on your game to join; the update comes through Steam.
How reliable is 测试123456789, and is it online now?
测试123456789 currently answers as online. Of note: the reported uptime places the last restart about 57 minutes ago. The records show 97% uptime over the last 3 full days: 70 of 72 hours up. Its earliest entry at Rust Server Stats is dated 25 October 2026.
What is the performance of 测试123456789 like?
Server fps averaged 155 over the last 48 hours; the low was 108. Buildings, deployables and the rest brought the entity count to a high of 75,699. Of note: memory use reached 3,251 MB. Lag, as players meet it, comes from low fps and an entity count on the rise.
Where does 测试123456789 operate from?
The name of 测试123456789 points to Asia, though no region tag is published. Where the machine stands is not looked up by Rust Server Stats; it shows where a server says it is. At 118.178.196.247:28015 stands the address.
The rules and map
The map for 测试123456789: which one is it?
测试123456789 runs a procedural map, generated by the game, of size 3,500 with seed 1573025114. The map repeats with the same size and seed; this page links to it on RustMaps.
What settings and rules does 测试123456789 run?
Nothing in the name of 测试123456789 gives a gather rate. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid: the standard game. Combat and raiding between players are permitted. Plugins or settings change the game; it appears under Modded in the browser. The plugin set is Oxide. VAC, Valve's anti-cheat, is disabled.
Population
How full does 测试123456789 get?
The record for 测试123456789 shows 1 players, against a capacity of 1. Over seven days the mean is 1 players, with a peak of 1. The busiest hour of the last 48 was 19:00 UTC, averaging 1 players.
What position does 测试123456789 hold among Rust servers?
On player hours over seven days 测试123456789 ranks #4,804, inside the top 22% of all ranked servers.
Tags, lists
测试123456789 sits in which Rust Server Stats lists and filters?
The Rust Server Stats lists 测试123456789 fits: Modded Rust servers. On the server list it comes up under these filters: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
The tags on 测试123456789: what do they signify?
gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): 1 is the number of slots; ts8 (Group limit): Set at the game default of 8 per team; v2635 (Protocol): Protocol 2635: joining needs the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code is not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Under Modded, because settings or plugins alter the game — that is the set of tags 测试123456789 publishes for the game's browser. At the top of this page are its current players, queue and world creation time, all taken from the tags.
Wipe schedule
What happens on 测试123456789 when wipe day arrives?
The average peak across recent wipes was 1 players. 1 hours after the latest wipe the crowd peaked, and 1 more were queued. Above half that peak until the next wipe: the crowd held in 100% of recent wipes.
The wipe timetable for 测试123456789: what does it show?
Wipes on 测试123456789 follow no fixed times, so no next wipe is forecast. The monthly force wipe falls on every Rust server alike, and Thursday 5 November at 19:00 UTC is the next one. The present world dates from 4 hours.
Joining the server
Which steps join 测试123456789?
Join on this page with Launch Rust, which opens Rust through Steam and connects you, or open the console with F1 and enter client.connect 118.178.196.247:28015. Of note: the server is full right now, so a queue is likely.