Telegram RegisterThe public register of Telegram
Telegram profile photo for rufwooff

Channel

rufwooff

@rufw00ff

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1,209subscribers

-2 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003125451641
TypeChannel
Username@rufw00ff
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/rufw00ff

Growth

1,1981,2111,204.56 August 2026 — 1,211 subscribers6 August 2026 — 1,211 subscribers6 August 2026 — 1,210 subscribers9 August 2026 — 1,208 subscribers12 August 2026 — 1,205 subscribers16 August 2026 — 1,203 subscribers18 August 2026 — 1,202 subscribers21 August 2026 — 1,201 subscribers25 August 2026 — 1,198 subscribers27 August 2026 — 1,209 subscribers3 September 2026 — 1,211 subscribers9 September 2026 — 1,209 subscribers1,2096 August 20269 September 2026
12 measurements spanning 34 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,196–1,213 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 00:001,209-2
3 Sept 2026, 07:081,211+2
27 Aug 2026, 23:421,209+11
25 Aug 2026, 00:591,198-3
21 Aug 2026, 11:491,201-1
18 Aug 2026, 20:471,202-1
16 Aug 2026, 05:551,203-2
12 Aug 2026, 20:341,205-3
9 Aug 2026, 16:011,208-2
6 Aug 2026, 23:451,210-1
6 Aug 2026, 08:471,211no change
6 Aug 2026, 07:031,211first reading

Engagement

4 posts held, back to 20 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 4 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 Aug 2026, 03:21 UTC≈181 views28 reactionsread 6 August 2026
Forwarded from @makivachanPhoto

ЗДАРОВА БАНДИТЫ, А ВОТ И У МЕНЯ ДЕНЬ РОЖДЕНЕВА 👅 Сегодня мне исполнилось 20 годиков жесть, а каналу целых 2 года 🥹 Хотела сказать спасибо большое ваще за все!!! Я не знаю представляете ли вы как я вас люблю, ну вот представьте ^^ Благодарю за все ваши комментарии, лайки, подарки, ну в общем спасибо, что вы существуете шладки ❤️ Обняла приподняла!👋

25 Jul 2026, 15:34 UTC≈439 views23 reactionsread 6 August 2026
Photo

В общем севодня мой др!!! Вместо очередной подборки своих красивих работ, которым сто тыщ лет, набрала скетщики кароче, так шо буду рада репосту🥰🥰🥰 (ну или выше подборку делала для портфолио дей, можно и её репостнуть хз, как хочите!!) 4276 3100 4178 9662 темные силы управляют моей рукой шо б оставитб свой сбер никого не заставляю, но мне будет писец приятна(⁠≧⁠▽⁠≦⁠)

21 Jul 2026, 23:36 UTC≈503 views39 reactionsread 6 August 2026
Photo

Едем к Амге Очень хочу ссать

20 Jul 2026, 11:56 UTC≈411 views34 reactionsread 6 August 2026
Forwarded from @silverheatherrPhoto

А у меня сегодня день рождения! Спасибо огромное всем кто следил и продолжает следить за моими картинками ✍️

Showing the 4 most recent of 4 posts we hold for @rufw00ff. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 6 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 9 September 2026 — this entry's latest reading, not the date you are reading this.

“rufwooff” (@rufw00ff), 1,209 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/rufw00ff.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.