Online 160.251.214.180:28015 checked 8m ago
Negitoro
Connect
srv = rust.server("160.251.214.180:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 best
srv.rank.plot(invert=True) # 1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 6 Oct, 13:08 UTC23d ago | 1 | NaN | running | 0 |
# 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.
display(srv.map, srv.info())
Map
6000 · seed 1159760689
- map
- Procedural Map
- size
- 6000
- seed
- 1159760689
Server
srv.info()- address
- 160.251.214.180:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Oct 2026, 13:08 UTC
- hostname
- –
- first seen
- 4 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 31/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 0/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 12/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 31/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 45/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Negitoro rank?
Rank #15,270 on seven-day player hours for Negitoro, within the top 69% of all ranked servers.
What population does Negitoro carry?
Current row: 0 players on Negitoro, against 50 slots. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on Negitoro?
Server fps over the last 48 hours averages 33; the floor is 16. Entity numbers reached 198,503, and that includes buildings, deployables and the rest. A high of 5,005 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on Negitoro?
The build is Rust network protocol 2634 and build 166652 on Linux, run by Negitoro. The protocol has to match before you can join, and Steam does the updating.
How reliable is Negitoro, and is it up?
Online is the state at the latest refresh for Negitoro. A restart about 6 days 5 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 4 October 2026.
Which location does Negitoro run from?
For Negitoro, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 160.251.214.180:28015 is its address.
Map and rules
Which rules apply on Negitoro, and what settings?
You will not find a gather rate in the string Negitoro. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Negitoro selected?
Negitoro runs a procedural map of size 6,000 with seed 1159760689, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does Negitoro wipe, and on what schedule?
A rhythm cannot be read from the wipes of Negitoro on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 23 days 16 hours ago.
What is wipe day on Negitoro like?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does Negitoro appear among Rust Data lists and filters?
These Rust Data lists include Negitoro: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Negitoro?
These tags are published by Negitoro and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to Negitoro?
Enter client.connect 160.251.214.180:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.