قسمت ۸ کلنگ و جارو منتشر شد! 🔥😂 این قسمت به قسمت اول مربوطه… 👀 و مهمتر از همه اینکه این قسمت، قسمت آخر این ماجراست! 😳🔥 اگه قسمتهای قبلی رو دیدی، پایان داستان رو از دست نده! 📤 ببین و برای رفیقت فوروارد کن! @kolangsho
🤬1

Channel
@kolangsho
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
438subscribers
-42 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002301365815 |
|---|---|
| Type | Channel |
| Username | @kolangsho |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/kolangsho |
Memes & entertainment — 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 39% 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 |
|---|---|---|
| 12 Oct 2026, 19:00 | 438 | -2 |
| 2 Oct 2026, 04:18 | 440 | -13 |
| 17 Sept 2026, 04:20 | 453 | -5 |
| 8 Sept 2026, 14:59 | 458 | -3 |
| 31 Aug 2026, 06:57 | 461 | -4 |
| 23 Aug 2026, 18:18 | 465 | -7 |
| 16 Aug 2026, 17:48 | 472 | -8 |
| 8 Aug 2026, 04:34 | 480 | no change |
| 7 Aug 2026, 18:22 | 480 | first reading |
20 posts held, back to 19 June 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 27 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
8 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 87.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 87.5% | |
| 🤬 | 1 | 12.5% |
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 7 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 8 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 19 June 2026 to 27 July 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.
قسمت ۸ کلنگ و جارو منتشر شد! 🔥😂 این قسمت به قسمت اول مربوطه… 👀 و مهمتر از همه اینکه این قسمت، قسمت آخر این ماجراست! 😳🔥 اگه قسمتهای قبلی رو دیدی، پایان داستان رو از دست نده! 📤 ببین و برای رفیقت فوروارد کن! @kolangsho
🤬1
قسمت ۷ کلنگ و جارو منتشر شد! 😄🔥 این قسمت رو ببین و برای اون رفیقت بفرست که باید حتماً ببینتش 😂 📤 ببین چند نفر این قسمت رو فوروارد میکنن! @kolangsho
🚀 اینترنت سریعتر و اتصال پایدارتر با Kolang VPN ✅ سرعت بالا ✅ اتصال آسان و فوری ✅ مناسب تلگرام، اینستاگرام، واتساپ و وبگردی ✅ پشتیبانی سریع ✅ سرویسهای متنوع و قیمت مناسب برای دریافت سرویس و مشاهده پلنها، وارد ربات شوید 👇 @kolangvpnbot
🎬 قسمت ششم «کلنگ و جارو» منتشر شد! این بار ماجرا عجیبتر، خندهدارتر و پرتنشتر از قبل شده! 😂🧹⛏️ کلنگ و جارو دوباره وارد دردسری شدن که معلوم نیست آخرش به کجا میرسه! تا آخر ببین و توی کامنتها بگو: بهنظرت ادامه این داستان چی میشه؟ 👀 📤 برای دوستات هم بفرست تا اونا هم حدس بزنن! @kolangsho
❤2
🎬 قسمت پنجم «کلنگ و جارو» منتشر شد! این قسمت هم پر از اتفاقهای عجیب، بحثهای بامزه و موقعیتهاییست که فقط از کلنگ و جارو برمیاد! 😂🧹⛏️ تا آخر ببین و توی کامنتها بگو: بهنظرت این بار حق با کدومشونه؟ 📤 برای دوستات هم بفرست تا اونا هم نظر بدن! #کلنگ_و_جارو #قسمت_پنجم #طنز #داستان_کمدی @kolangsho
❤1
🎬 قسمت چهارم «کلنگ و جارو» منتشر شد! اگر دنبال چند دقیقه حال خوب و خندهاید، این قسمت را از دست ندهید. 😄 تماشا کنید، لذت ببرید و برای دوستانتان هم بفرستید. ❤️ @kolangsho
❤1
🚀 اینترنت سریع و پایدار با KolangVPN 🔥 دیگه با قطعی و سرعت پایین خداحافظی کن! با KolangVPN تجربهای سریع، مطمئن و راحت برای استفاده روزمره، شبکههای اجتماعی و کار داشته باش 🌐 ✅ سرعت بالا ✅ اتصال پایدار ✅ IP ثابت ✅ پشتیبانی سریع ✅ مناسب چند کاربر 📦 پلنهای ویژه: 🔹 ۵۰ گیگ | ۲۴۹ هزار تومان 🔹 ۱۰۰ گیگ | ۳۹۹ هزار تومان 🔹 ۲۰۰ گیگ | ۴۹۹ هزار تومان 🔹 ۴۰۰ گیگ | ۸۹۹ هزار تومان 🔥 همین حالا سفارش بده و همیشه آنلاین بمون 📢 کانال K…
🎬 قسمت سوم داستان «کلنگ و جارو» منتشر شد! 😍 این قسمت رو برای دوستاتون بفرستید تا با هم بخندید و شاد باشید ❤️😂 منتظر باشید... 🔥 @kolangsho
🪓 داستان «کلنگ و جارو» قسمت اول منتشر شد! این قسمت رو برای دوستانت بفرست تا اونا هم ببینن 😍 ادامه داستان و قسمتهای بعدی بهزودی در کانال منتشر میشه 🔥 منتظر ماجراهای جدید کلنگ و جارو باشید... @kolangsho
@kolangsho
❤1
بهترین بازیکن فوتبال از دیدگاه هوش مصنوعی @kolangsho
❤1
🔴تو آسمون روسیه یه تیکه ابر رنگینکمونی دیده شد که شباهت زیادی به نقشه ایران داره @kolangsho
Showing the 12 most recent of 20 posts we hold for @kolangsho. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“kolangsho” (@kolangsho), 438 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/kolangsho.
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.