Telegram RegisterThe public register of Telegram
Telegram profile photo for #rf0x1dgang

Channel

#rf0x1dgang

@rf0x1dgang

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

10subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001350258206
TypeChannel
Username@rf0x1dgang
DescriptionГенг генг генг (бенг) чят в кноп очке
Created12 February 2020measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/rf0x1dgang

Growth

106 August 2026 — 10 subscribers12 August 2026 — 10 subscribers6 August 202612 August 2026
2 measurements spanning 6 days. 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 9–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 08:4510no change
6 Aug 2026, 20:2410first reading

Engagement

15 posts held, back to 12 February 2020the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 15 posts for this entry, the most recent from 10 May 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Links
1

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

10 May 2022, 13:13 UTC276 viewsread 12 August 2026

РфокседГенг таки не все. На последнем издыхании серия уморительных постов мне похуй. Втостерс тим распался, от лбо отвернулись все к хуям, именно поэтому: https://t.me/rfoxy/14070 https://t.me/rfoxy/14139 Вот теперь точно все. Peace. Артур Скубей помой голову.

Signed рфоксед

7 Jan 2022, 13:26 UTC360 viewsread 12 August 2026

откуда на постах по 700 просмотров

Signed рфоксед

7 Jan 2022, 13:18 UTC358 viewsread 12 August 2026

люди которые не знают: 😂 люди которые знают: 😳

Signed рфоксед

26 May 2020, 12:14 UTC≈1,330 viewsread 12 August 2026

РфокседГенг официально все. С втостерс тим мы помирились ещё давно, все нормально.

Signed рфоксед

24 Mar 2020, 20:51 UTC930 viewsread 12 August 2026
Forwarded from @rf0x3d

Короче, новости хуже чем бомбежка Донбасса. Все люди, которые со мной общались или которые имеют в нике хештег #rf0x1dgang получили бан от Руби(это токсик такой) во всех чатах, связанных с командой втостерс(где у него админка была, конечно же) и, к сожалению, данное решение не будет пересмотрено, т.к меня по самым тупым причинам подозревают в сливе билда альфы втостерс. Увы, я ничего с этим поделать не могу. Держимс

Signed рфоксед хайповый #rf0x1dgang

25 Feb 2020, 07:09 UTC≈1,210 viewsread 12 August 2026
Sticker

Sticker, posted without a caption

Signed рфоксед #rf0x1dgang

20 Feb 2020, 12:25 UTC≈1,030 viewsread 12 August 2026
Photo

Photo, posted without a caption

Signed рфоксед #rf0x1dgang

20 Feb 2020, 12:25 UTC861 viewsread 12 August 2026

Типичное животное из лучата. Да я таких как ты убивал нахуй во Вьетнаме, сука

Signed рфоксед #rf0x1dgang

12 Feb 2020, 09:30 UTC896 viewsread 12 August 2026

Ну или куда нибудь в другое место, можно вообще на аву

Signed рфоксед #rf0x1dgang

12 Feb 2020, 09:29 UTC858 viewsread 12 August 2026

Шоб быть одним из лучших (хз т9 предложил) нада короче в ник это: #rf0x1dgang

Signed рфоксед #rf0x1dgang

Showing the 12 most recent of 15 posts we hold for @rf0x1dgang. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“#rf0x1dgang” (@rf0x1dgang), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/rf0x1dgang.

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.