Working its way up from the back of the class: #15,891 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
50/ 100
D
Holding steady: up 67 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h.
The force wipe · high confidence
wipe-day peak10players, last three wipes
Coming wipes
7d 2hThu 5 Nov, 19:00 UTCFW
35d 2hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 10, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 19 Sep, 22:59 UTC39d ago
10
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Rust Time Baby Woo. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 63.135.165.33:9270.
How reliable is Rust Time Baby Woo, and is it up?
At this moment, Rust Time Baby Woo is offline; the last time it was seen was 20 days 6 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
On what Rust version does Rust Time Baby Woo sit?
Rust network protocol 2633 and build 164530 on Linux is what Rust Time Baby Woo runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Rust Time Baby Woo wipe its map?
Once a month, Rust Time Baby Woo wipes with the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 39 days 17 hours have passed since this world was made. Its tags record that it wipes monthly.
What happens on Rust Time Baby Woo when wipe day arrives?
Across its recent wipes, the busiest moments averaged 10 players. Peak numbers came 4 hours into the latest wipe.
Population
Where does Rust Time Baby Woo place in the wider field of Rust servers?
Over the last seven days, Rust Time Baby Woo has #15,891 for player hours, in the top 72% of all ranked servers.
Is Rust Time Baby Woo a busy server?
The last sighting of Rust Time Baby Woo was 20 days 6 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on Rust Time Baby Woo?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp24 (Max players): 24 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them are the tags Rust Time Baby Woo publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Rust Time Baby Woo?
These Rust Server Score lists count Rust Time Baby Woo among them: Best community servers, graded and Vanilla Rust servers, graded. These filters bring it up on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
Which rules does Rust Time Baby Woo enforce, and what are its settings?
The name of Rust Time Baby Woo gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. Vanilla is what it calls itself: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Rust Time Baby Woo?
Rust Time Baby Woo runs a game-generated procedural map at size 2,300, seed 691492370. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto Rust Time Baby Woo?
Enter client.connect 63.135.165.33:9270 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp24,ptrak,$r?,v2633,^m,^v,gmrust,cs164530,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp24
Max players24 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).