Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐂𝐇𝐁𝐁𝐅𝐗

Channel

𝐂𝐇𝐁𝐁𝐅𝐗

@chbbfx11

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

264subscribers

-54 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003284676832
TypeChannel
Username@chbbfx11
CreatedBetween 1 October 2025 and 28 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/chbbfx11

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 92% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

2643182917 August 2026 — 318 subscribers7 August 2026 — 316 subscribers8 August 2026 — 316 subscribers15 August 2026 — 308 subscribers22 August 2026 — 296 subscribers30 August 2026 — 280 subscribers8 September 2026 — 271 subscribers15 September 2026 — 264 subscribers7 August 202615 September 2026
8 measurements spanning 39 days, net -54. 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 256–326 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 19:19264-7
8 Sept 2026, 23:37271-9
30 Aug 2026, 18:28280-16
22 Aug 2026, 22:14296-12
15 Aug 2026, 01:37308-8
8 Aug 2026, 07:34316no change
7 Aug 2026, 22:54316-2
7 Aug 2026, 18:41318first reading

Engagement

20 posts held, back to 7 July 2026 — the 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Aug 2026, 12:40 UTC19 viewsread 8 August 2026
Forwarded from @leoger0

‼️ПРОДАЮ КАНАЛ ‼️ Я продаю данный канал. Честно, я не знаю за сколько продают подобные каналы. На канале на данный момент 260 подписчиков и 1.024 звезды(я хз как их выводить,у меня ошибка). Всё таки это не мало. Поэтому продаю за 350-500 звёзд. Союзы,друзья и ТД прошу рассыл.

1 Aug 2026, 11:49 UTC32 viewsread 8 August 2026

🤍🤍🤍🤍🤍🤍🤍 Итак, как многие уже поняли этот канал перестал функционировать, поэтому Диана создала новый Вести его мы начнём чуть позже, сейчас надо всё доделать Вот ссылка: @diaylairSp Те кто хочет сохранить союз свяжитесь с нами Всем спасибо 🖤

Signed Сталкер

11 Jul 2026, 17:17 UTC66 viewsread 8 August 2026

Чтоб тебе жилось долго и счастливо, не убейся, не подавись, не споткнись и чтоб тебя не сбиз камаз

Signed Сталкер

11 Jul 2026, 17:16 UTC60 viewsread 8 August 2026

Знаешь, нынче расплодились летающие кирпичи, ходи и оглядывайся, тварь

Signed Сталкер

11 Jul 2026, 17:14 UTC58 viewsread 8 August 2026

Надо, вернулся спустя 100 лет и говорит, что уходит 💔

Signed Сталкер

8 Jul 2026, 07:15 UTC56 viewsread 8 August 2026

Построятся не сдохнуть в дороге 😟

8 Jul 2026, 06:35 UTC40 viewsread 8 August 2026

Ну, не всё так плохо, как я думала. Я просто сплю всю дорогу🤷‍♀️

Showing the 12 most recent of 20 posts we hold for @chbbfx11. 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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“𝐂𝐇𝐁𝐁𝐅𝐗” (@chbbfx11), 264 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/chbbfx11.

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.