Channel
@exehub_ex
On this record: Topic · Growth · Engagement · Posts · Cite this entry
722subscribers
-169 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001788421159 |
|---|---|
| Type | Channel |
| Username | @exehub_ex |
| Created | 19 October 2022 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/exehub_ex |
Marketing & affiliate — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 10:22 | 722 | -22 |
| 19 Sept 2026, 12:17 | 744 | -45 |
| 10 Sept 2026, 13:01 | 789 | -31 |
| 31 Aug 2026, 18:43 | 820 | -7 |
| 24 Aug 2026, 21:07 | 827 | -15 |
| 16 Aug 2026, 20:36 | 842 | -43 |
| 8 Aug 2026, 09:36 | 885 | -6 |
| 8 Aug 2026, 01:05 | 891 | no change |
| 7 Aug 2026, 16:35 | 891 | first reading |
4 posts held, back to 19 October 2022 — 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 4 posts for this entry, the most recent from 22 August 2025. An engagement rate over an empty window would be a number about nothing.
❗️Остерегайтесь наших фейков ❗️ 🤓Всегда проверяйте имя пользователя! Один единственный официальный аккаунт ExeHub - @Exehub_SMMM 🌝Если вам пишут с другого аккаунта под нашим именем - кидайте сразу в ЧС.
😎На связи ExeHub Решили порадовать себя и вас новым, приятным для глаз дизайном🐸 Вопрос для тех, кто с нами уже продолжительное время: какой лучше? 👍 - Новый 👎 - Старый Спасибо всем за мнения, ко всем прислушаемся! На связи: @Exehub_SMMM
📈 BlackRock выделяет биткоин как более привлекательный актив 💹 Крупнейшая в мире управляющая компания BlackRock опубликовала аналитический обзор, в котором биткоин назван более привлекательным для инвесторов по сравнению с традиционными активами. В отчетe указаны ключевые факторы, способствующие росту BTC: ограниченное предложение, уникальные свойства как альтернативного денежного инструмента и преимущества в услови…
Channel created
Showing the 4 most recent of 4 posts we hold for @exehub_ex. 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.
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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“Exehub” (@exehub_ex), 722 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/exehub_ex.
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.