Channel
@boston_cIub
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2,025subscribers
-99 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002394360544 |
|---|---|
| Type | Channel |
| Username | @boston_cIub |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/boston_cIub |
Sports — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 15 Sept 2026, 23:19 | 2,025 | -11 |
| 12 Sept 2026, 03:00 | 2,036 | -11 |
| 7 Sept 2026, 22:18 | 2,047 | -15 |
| 2 Sept 2026, 14:17 | 2,062 | -3 |
| 30 Aug 2026, 16:44 | 2,065 | -5 |
| 27 Aug 2026, 06:35 | 2,070 | -10 |
| 23 Aug 2026, 22:18 | 2,080 | -13 |
| 20 Aug 2026, 07:57 | 2,093 | -7 |
| 17 Aug 2026, 15:18 | 2,100 | -9 |
| 14 Aug 2026, 07:27 | 2,109 | -8 |
| 10 Aug 2026, 23:45 | 2,117 | -6 |
| 8 Aug 2026, 06:11 | 2,123 | -1 |
| 7 Aug 2026, 14:47 | 2,124 | no change |
| 7 Aug 2026, 14:03 | 2,124 | first reading |
20 posts held, back to 5 August 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
4 игры. Джейлен Брансон — MVP финала 2025/26. Это значит: стабильность в решающие моменты и лидерство, на котором строится команда. Для фанатов — уверенность в будущем Никс; для ставок/фантазий — ориентир при выборе капитана и стратегии на следующий сезон 🏀
Posted without readable text
Джеймс Харден стал первым в истории НБА с 50 очками и 15 ассистами в финале конференции. Это важно: показывает не только снайперский масштаб, но и умение творить для команды. Для ставок и анализа — сигнал, что Харден доминирует и тянет игру на себя. 🏀
Posted without readable text
Суть: Пистонс готовы предложить Джейлену Дюрену максимальное продление — хотят зафиксировать ядро. Это как продлить аренду вожатого, который собрал команду: стабильно, чтобы строить вокруг него атакующую и защитную систему. Польза — ясность ротации и рост молодых партнёров. 🏀
Posted without readable text
Лука Дончиć в первом раунде установил рекорд плей‑офф по триочковым — 9 в одном матче. Это полезно для болельщиков: показывает, как атака команды строится вокруг его дистанционной угрозы и почему соперникам нужно менять тактику защиты. 🏀
Posted without readable text
Вембаньяма собрал рекордные 14 подборов в решающем матче финала. Это не просто цифра — контроль щита решает ритм игры. Как в уборке дома: кто быстрее уберёт мусор, тот задаёт порядок. Больше подборов — больше шансов на владение и очки. 🏀
Posted without readable text
2 города — Сиэтл и Лас-Вегас — в прицеле расширения НБА. Для болельщика это больше матчей, новые соперники и шанс увидеть звёзд в другом городе. Ближе доступ к видам, возможны новые дерби и рост ценности билетов в регионах. 🏀
Posted without readable text
Showing the 12 most recent of 20 posts we hold for @boston_cIub. 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 1 registered channel — 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“𝐁𝐎𝐒𝐓𝐎𝐍' | Клуб🏀” (@boston_cIub), 2,025 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/boston_cIub.
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.