Channel
@boston_bo_ston_24
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
21,605subscribers
+20,806 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001852145842 |
|---|---|
| Type | Channel |
| Username | @boston_bo_ston_24 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 3 times, most recently 30 October 2026 |
| On Telegram | t.me/boston_bo_ston_24 |
Local community — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 12:57 | 21,605 | -1 |
| 25 Oct 2026, 20:35 | 21,606 | -2 |
| 24 Oct 2026, 19:17 | 21,608 | -1 |
| 23 Oct 2026, 18:46 | 21,609 | -4 |
| 21 Oct 2026, 11:11 | 21,613 | -1 |
| 20 Oct 2026, 07:57 | 21,614 | -2 |
| 19 Oct 2026, 05:26 | 21,616 | -7 |
| 18 Oct 2026, 06:30 | 21,623 | -6 |
| 17 Oct 2026, 06:15 | 21,629 | -8 |
| 16 Oct 2026, 02:40 | 21,637 | -6 |
| 15 Oct 2026, 03:16 | 21,643 | +20,042 |
| 12 Oct 2026, 07:21 | 1,601 | +1,159 |
| 2 Oct 2026, 12:20 | 442 | -110 |
| 17 Sept 2026, 10:15 | 552 | -198 |
| 9 Sept 2026, 18:56 | 750 | -10 |
| 24 Aug 2026, 10:35 | 760 | -1 |
| 17 Aug 2026, 11:06 | 761 | -38 |
| 10 Aug 2026, 09:45 | 799 | no change |
| 10 Aug 2026, 09:31 | 799 | first reading |
4 posts held, back to 2 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 4 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Bo‘ston tumanida suyultirilgan gaz ta’minoti ustidan nazorat kuchaytirilmoqda Suyultirilgan gaz bilan barqaror ta’minlash aholining yoqilg‘iga bo‘lgan ehtiyojini qoplash, ta’minot uzluksizligini ta’minlash hamda iste’molchilarga ko‘rsatilayotgan xizmatlar sifatini oshirishda muhim ahamiyatga ega. Shu bois Andijon viloyatida suyultirilgan gaz ballonlarini belgilangan tartibda yetkazib berish, bo‘sh ballonlarni o‘z va…
Payshanba - Yoshlar kuni munosabati bilan Bo‘ston tuman prokurori Bahodirjon Usmonov tomonidan yoshlar va ularning oila aьzolari bilan uchrashuv o‘tkazildi. Uchrashuv davomida yoshlarning muammolari va takliflari tinglanib, ularni qo‘llab-quvvatlash masalalari atroflicha muhokama qilindi.
#TargibotchilarForumi #VijdonErkinligi #Yangiruhiyat “Vijdon erkinligi — huquqiy kafolat va jamiyat barqarorligining asosi” mavzusidagi Respublika “Targ‘ibotchilar” guruhi a’zolari Boʻston tumanida oʻz targʻibot ishlarini olib bordilar. Boʻston tumani hokimligi majlislar zalida Ulugʻnor va Boʻston tumanidagi hotin qizlar faollari, otinoyilar va mahalla faollariga oʻz targʻibot ishlarini olib bordilar va Oila marka…
#Jarayon Bo‘ston tumanida umumxalq hashari qizg‘in ruhda davom etmoqda. Hududlarda obodonlashtirish va ozodalik ishlari uyushqoqlik bilan olib borilib, ko‘chalar, jamoat maskanlari hamda atrof-muhit tartibga keltirilmoqda. Ezgu hashar ishlari aholi birdamligi va hamjihatligini yana bir bor namoyon etmoqda.
Showing the 4 most recent of 4 posts we hold for @boston_bo_ston_24. 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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“BO'STON24 | TEZKOR XABARLAR” (@boston_bo_ston_24), 21,605 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/boston_bo_ston_24.
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.