🗓 جمعه ۰۶ شهریور ماه ۱۴۰۵ ◀️با انتقال رطوبت از سرخ به منطقه فردا و پس فردا بصورت نقطهای و محلی بارش داریم. 🌐 Telegram: t.me/kashohava 🌐 Rubika: Rubika.ir/kashohava1
❤3🤔1

Channel
@kashohava
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
7,741subscribers
-17 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001009983640 |
|---|---|
| Type | Channel |
| Username | @kashohava |
| Created | Between 1 November 2015 and 31 January 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/kashohava |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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 |
|---|---|---|
| 14 Sept 2026, 18:18 | 7,741 | -2 |
| 11 Sept 2026, 07:58 | 7,743 | -4 |
| 6 Sept 2026, 14:59 | 7,747 | -5 |
| 2 Sept 2026, 03:24 | 7,752 | +2 |
| 29 Aug 2026, 23:14 | 7,750 | -5 |
| 26 Aug 2026, 16:34 | 7,755 | -3 |
| 20 Aug 2026, 10:07 | 7,758 | no change |
| 19 Aug 2026, 12:15 | 7,758 | first reading |
32 posts held, back to 9 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 7 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 32 (9 August 2026 – 28 August 2026) |
| Views total | 29,235 |
| Reactions total | 114 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 20:44 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 6 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.
197 reactions across 32 posts, in 10 distinct kinds. The most used accounts for 82.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 162 | 82.2% | |
| 😢 | 17 | 8.63% | |
| 👎 | 5 | 2.54% | |
| 🤔 | 3 | 1.52% | |
| 🤩 | 3 | 1.52% | |
| 👍 | 2 | 1.02% | |
| 😍 | 2 | 1.02% | |
| 👀 | 1 | 0.508% | |
| 🔥 | 1 | 0.508% | |
| 🙏 | 1 | 0.508% |
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 32 of the 32 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 197 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 9 August 2026 to 28 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.
🗓 جمعه ۰۶ شهریور ماه ۱۴۰۵ ◀️با انتقال رطوبت از سرخ به منطقه فردا و پس فردا بصورت نقطهای و محلی بارش داریم. 🌐 Telegram: t.me/kashohava 🌐 Rubika: Rubika.ir/kashohava1
❤3🤔1
🗓 جمعه ۰۶ شهریور ماه ۱۴۰۵ الگوی وزش باد فردا شنبه ✔️همزمان با فعالیت سامانه بارشی در منطقه شاهد تندبادهای لحظهای خواهیم بود. ⚠️❌جهت جلوگیری از خسارات احتمالی تمهیدات لازمه بکارگیرد. 🌐 Telegram: t.me/kashohava 🌐 Rubika: Rubika.ir/kashohava1
❤3
🗓 جمعه ۰۶ شهریور ماه ۱۴۰۵ الگوی تجمع بارش دوشنبه ۰۹ شهریور ✔️طی این روز بارش ها به شمال استان آذربایجان غربی محدود می شوند، البته که در شب و بامداد دوشنبه احتمال رگبارهای محلی علی الخصوص در ارتفاعات مهیاست. 🌐 Telegram: t.me/kashohava 🌐 Rubika: Rubika.ir/kashohava1
❤5
🗓 جمعه ۰۶ شهریور ماه ۱۴۰۵ الگوی تجمع بارش پس فردا یکشنبه ۰۸ شهریور ✔️در روز یکشنبه همچنان بارندگی ها در وسعت بیشتری و بصورت نقطهای ادامه خواهند داشت. ☑️طی این روز در استان های کردستان، کرمانشاه و شمال ایلام هم بصورت نقطهای و محلی بارش داریم. 🌐 Telegram: t.me/kashohava 🌐 Rubika: Rubika.ir/kashohava1
❤6
🗓 جمعه ۰۶ شهریور ماه ۱۴۰۵ الگوی تجمع بارش فردا شنبه ۰۷ شهریور ✔️بصورت نقطهای شاهد رگبارهای تابستانه بهمراه رعدوبرق و وزش باد شدید خواهیم بود. 🌧بارش های تابستانی نقطهای هستند در نتیجه نمی توان محل دقیق بارندگی را مشخص کرد در نتیجه کل منطقه در معرض ناپایداری جوی هستند. 🌐 Telegram: t.me/kashohava 🌐 Rubika: Rubika.ir/kashohava1
❤6
🗓 پنجشنبه ۰۵ شهریور ماه ۱۴۰۵ سیل مرگبار در نپال؛ صدها نفر مفقود شدند ✔️بر اساس گزارش های منتشر شده، این حادثه در تاریخ ۲۶ آگوست برابر با ۰۴ شهریور پس از فروریختن بخشی از یک یخچال طبیعی در ارتفاعات هیمالیا و ورود حجم عظیمی از آب، سنگ، گل و لای و بقایای یخ به دره رودخانه Lhende Khola رخ داده است. این جریان سپس وارد رودخانههای منطقه از جمله Bhote Koshi و Trishuli شد و با سرعت زیادی مناطق پایین دست را درنوردید. 🔴آ…
❤7😢7
🗓 پنجشنبه ۰۵ شهریور ماه ۱۴۰۵ منتظر رگبارهای تابستانی در روزهای ابتدایی هفته آینده باشید 🔺 با عقب نشینی پرفشار جنب حاره ای و نفوذ ناوه تراز میانی جو، طی روزهای شنبه و یکشنبه هفته آینده، استان های آذربایجان غربی، کردستان، کرمانشاه و بخش هایی از ایلام تحت تأثیر فعالیت سامانه بارشی تابستانه قرار خواهند گرفت. 🌧️ پیش بینی می شود طی این مدت، رگبارهای محلی باران همراه با رعدوبرق های نقطه ای و تندبادهای لحظه ای در…
❤8👍1
🗓 پنجشنبه ۰۵ شهریور ماه ۱۴۰۵ آغاز کاهش دمای روزانه و خودنمایی دماهای شبه پاییزی ✔️طبق بررسی آخرین الگوهای جوی از روز دوشنبه هفته آینده شاهد افت محسوس دما در سطح منطقه خواهیم بود. 🔹پیش بینی می شود از امروز تا روز یکشنبه ۰۸ شهریور دما تغییرات جزئی نسبت به روزهای قبل داشته باشد ولی کاهش اصلی دما برای روز دوشنبه به بعد خواهد بود. 🔹قابل ذکر است که انتظار می رود ۲ الی ۶ درجه کاهش دمای روزانه داشته باشیم و همچنین شدت کا…
❤6👍1
🗓 چهارشنبه ۰۴ شهریور ماه ۱۴۰۵ 🌧هم اکنون ـ رگبار باران در سلیمانیه اقلیم کردستان 🌐 Telegram: t.me/kashohava 🌐 Rubika: Rubika.ir/kashohava1
❤15
🗓 سهشنبه ۰۳ شهریور ماه ۱۴۰۵ سقوط دمای شبانه و آغاز هوای پاییزی 🔹از فردا شب، کاهش دما در سطح کل منطقه استارت می خورد و هوای سرد شبانه حاکم می شود. ✔️پیش بینی می شود شاهد افت ۴ الی ۷ درجه ای دما باشیم البته در برخی شب ها نوسانات خواهیم داشت. 🌐 Telegram: t.me/kashohava 🌐 Rubika: Rubika.ir/kashohava1
❤12
🗓 سهشنبه ۰۳ شهریور ماه ۱۴۰۵ ✔️ با توجه به افزایش سرعت وزش باد و احتمال وقوع تندبادهای لحظه ای، توصیه می شود برای جلوگیری از حوادث احتمالی، اقدامات لازم را انجام دهید. 🔸 از پارک کردن خودروها در زیر درختان کهنسال و سازه های ناپایدار خودداری کنید. 🔸 نسبت به احتمال سقوط اشیاء، مصالح ساختمانی و اجسام سبک از ارتفاعات و ساختمان های نیمه کاره توجه داشته باشید. 🔸 در زمان وقوع تندباد، از قرار گرفتن در مجاورت درختان، تا…
❤5
🗓 سهشنبه ۰۳ شهریور ماه ۱۴۰۵ 💨مطابق با الگوهای جوی از فردا شاهد آغاز افزایش سرعت وزش باد در سطح کل منطقه خواهیم بود. ✔️استان های آذربایجان غربی و کردستان هسته اصلی تندبادهای لحظهای می باشد. ☑️پیش بینی می شود این وضعیت در روزهای آینده همچنان تداوم داشته و هفته آینده برسرعت آن افزوده شود. 🌐 Telegram: t.me/kashohava 🌐 Rubika: Rubika.ir/kashohava1
❤5
Showing the 12 most recent of 32 posts we hold for @kashohava. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“هواشناسی سردشت و اطراف” (@kashohava), 7,741 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/kashohava.
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.