Channel
@bxdes
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
800subscribers
+15 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001507190548 |
|---|---|
| Type | Channel |
| Username | @bxdes |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/bxdes |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 10 Sept 2026, 03:21 | 800 | +2 |
| 31 Aug 2026, 20:13 | 798 | +3 |
| 19 Aug 2026, 03:35 | 795 | +8 |
| 12 Aug 2026, 22:13 | 787 | +2 |
| 6 Aug 2026, 15:34 | 785 | no change |
| 6 Aug 2026, 05:04 | 785 | first reading |
20 posts held, back to 31 May 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 3 August 2026. An engagement rate over an empty window would be a number about nothing.
5 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 60.0% | |
| 👎 | 1 | 20.0% | |
| 🔥 | 1 | 20.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 6 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 May 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
предварительно #weekly мероприятия Дайджест на неделю #w33 10.08 — 16.08 (все события - по тегу в группе PM дивергент) Москва пн🗓 10.08 в 19:00 Bitmanager ai. Voice AI Dev Meetup 1: голосовые технологии в продакшене https://t.me/div_conv/21/11119 вт🗓 11.08 в 19:00 Bitmanager ai. Agentic AI Dev Meetup 1: AI-агенты в продакшене https://t.me/div_conv/21/11120 чт🗓 13.08 в 12:30 Investor Games Club. 14-й баттл стартапов…
#product_weekly Дайджест на неделю #w32 03.08 — 09.08 Москва вт🗓 04.08 в 17:00 МШУ Сколково. Кризис как метод: как научить команду выигрывать в условиях нестабильности https://t.me/div_conv/33/11129 04.08 в 19:00 Сбер. Новая эра клиентского опыта https://t.me/div_conv/2/11085 04.08 в 19:00 Стартап-кафе. Один за всех больше не работает https://t.me/div_conv/33/11106 🌐онлайн 03.08 -— 07.08 Product School. AI Builder…
#weekly мероприятия Дайджест на неделю #w32 03.08 — 09.08 (все события - по тегу в группе PM дивергент) Москва пн🗓 03.08 в 11:00 Технопарк Сколково. ИИ-завтрак. ИИ для HR и HRD https://t.me/div_conv/242/11082 вт🗓 04.08 в 17:00 МШУ Сколково. Кризис как метод: как научить команду выигрывать в условиях нестабильности https://t.me/div_conv/33/11129 04.08 в 19:00 Сбер. Новая эра клиентского опыта https://t.me/div_conv/2…
#product_weekly Дайджест на неделю #w31 27.07 — 02.08 Москва ср🗓 29.07 в 19:00 MBA “Трансформация”. Искажение стратегических решений: почему правильные данные не гарантируют правильного выбора https://t.me/div_conv/242/11043 чт🗓 30.07 в 18:40 МШУ Сколково. Что останется? Управление продуктовой командой и ее состав в эпоху ИИ https://t.me/div_conv/2/11029 30.07 в 19:00 Немного продакт. Product Fuckup Night: НП х Зву…
#weekly мероприятия Дайджест на неделю #w31 27.07 — 02.08 (все события - по тегу в группе PM дивергент) Москва ср🗓 29.07 в 19:00 Мегафон. MF Spark Camp: 4 огня инноваций https://t.me/div_conv/21/11066 29.07 в 18:30 Сбер. Вечеринка Гига Фан https://t.me/div_conv/21/11088 29.07 в 19:00 MBA “Трансформация”. Искажение стратегических решений: почему правильные данные не гарантируют правильного выбора https://t.me/div_co…
❤1👎1
#product_weekly Дайджест на неделю #w30 20.07 — 26.07 Москва ср🗓 22.07 в 10:00 QSoft. Сколько продаж теряет бизнес без AI-поиска? https://t.me/div_conv/21/11000 чт🗓 платно 23.07 в 19:00 Backlog BBQ — French edition https://t.me/div_conv/2/10964 23.07 в 19:30 ДаДаТа. От промпта к полномочиям: как AI-агенты входят в юридически значимые процессы компаний https://t.me/div_conv/21/10999 сб🗓 25.07 в 12:00 Яндекс. Produc…
#weekly мероприятия Дайджест на неделю #w30 20.07 — 26.07 (все события - по тегу в группе PM дивергент) Москва вт🗓 21.07 в 11:00 Совет АПКИТ. Портрет российского IT-рынка: тренды, аудитория, инструменты https://t.me/div_conv/21/11008 ср🗓 22.07 в 10:00 QSoft. Сколько продаж теряет бизнес без AI-поиска? https://t.me/div_conv/21/11000 чт🗓 23.07 в 18:00 Yandex Cloud. Yandex DataLens: BI-аналитика без компромиссов https…
🔥1
#product_weekly мероприятия Дайджест на неделю #w29 13.07 — 19.07 Москва ср🗓 15.07 в 11:00 МБМ. Стратегия развития бизнеса: перезагрузка https://t.me/div_conv/2/10995 вс🗓 19.07 в 10:00 Сбер. AI-Native подход к продукту https://t.me/div_conv/2/10989 пт🗓Новосибирск 17.07 в 18.00 Контур. Как не перестараться с новыми технологиями https://t.me/div_conv/12/10979 🌐онлайн 13.07 в 19:00 Понедельник x Anna Money. Продукты …
❤1
#weekly мероприятия Дайджест на неделю #w29 13.07 — 19.07 (все события - по тегу в группе PM дивергент) Москва пн🗓 13.07 в 19:30 Фронтир. Индекс менеджмента. Управленческие навыки руководителей: уровень владения и приоритеты развития https://t.me/div_conv/33/10980 вт🗓 14.07 в 18:00 Сбер. Android Meetup https://t.me/div_conv/21/10981 ср🗓 15.07 в 11:00 МБМ. Стратегия развития бизнеса: перезагрузка https://t.me/div_co…
#product_weekly Дайджест на неделю #w28 06.07 — 12.07 Москва ср🗓 08.07 в 18:00 Стартап кафе. Внедрение OKR: как раскрыть потенциал компании https://t.me/div_conv/4/10947 08.07 в 19:00 MBA “Трансформация”. Почему эффективная лидогенерация —это критическая маркетинговая ошибка? https://t.me/div_conv/242/10937 08.07 в 19:00 ЦУ. Встреча с руководителями магистерских программ ЦУ https://t.me/div_conv/242/10954 сб🗓 11.0…
#weekly мероприятия Дайджест на неделю #w28 06.07 — 12.07 (все события - по тегу в группе PM дивергент) Москва ср🗓 08.07 в 18:00 Стартап кафе. Внедрение OKR: как раскрыть потенциал компании https://t.me/div_conv/4/10947 08.07 в 19:00 Т1. ИИ: ожидания и реальность, истории из практики https://t.me/div_conv/21/10946 08.07 в 19:00 DUC meetup /5: домашняя инфра, агент для кластера и новое в Deckhouse https://t.me/div_…
#product_weekly мероприятия Дайджест на неделю #w27 29.06 — 05.07 Москва ср🗓 01.07 в 18:30 Сбер. Архитектурный подход в AI Disrupt PDLC https://t.me/div_conv/21/10902 01.07 в 19:20 Agora. Агенты съели промпты: инженерный взгляд на новый GenAI-уклад https://t.me/div_conv/21/10903 сб-вс🗓 04.07, 05 07 в 11:00 Интенсив по аналитике ЦУ × Авито https://t.me/div_conv/242/10912 🌐онлайн 30.06 в 13:00 Сколково. Ой, перестал…
Showing the 12 most recent of 20 posts we hold for @bxdes. 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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“BX - business of experience” (@bxdes), 800 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/bxdes.
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.