Channel
@tabiat_zagors
On this record: Growth · Engagement · Posts · Citations · Cite this entry
273subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001059966511 |
|---|---|
| Type | Channel |
| Username | @tabiat_zagors |
| Created | Between 1 May 2016 and 31 January 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/tabiat_zagors |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 02:38 | 273 | -4 |
| 6 Aug 2026, 23:31 | 277 | no change |
| 6 Aug 2026, 16:54 | 277 | first reading |
4 posts held, back to 27 July 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 pageof 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 6 August 2026 |
|---|---|
| Posts held | 4 (27 July 2026 – 6 August 2026) |
| Views total | 4,775 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 23:31 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.
🖤🏴 به نام خدا ««هَلْ جَزَاءُ الْإِحْسَانِ إِلَّا الْإِحْسَانُ» «آیا پاداش نیکی، جز نیکی است؟»» 🏴 موکب مردمی خادمالحسین (ع) گروه جهادی صاحبالزمان (عج) 📍 مستقر در گردنه قلاجه ـ شهرستان گیلانغرب اربعین حسینی ۱۴۰۵ موکب مردمی خادمالحسین (ع) از ۴ تا ۱۵ مردادماه ۱۴۰۵ در گردنه قلاجه شهرستان گیلانغرب، با افتخار میزبان زائران اباعبدالله الحسین (ع) بود و بهصورت شبانهروزی و بیوقفه در مسیر خدمت به زائران قدم برداشت. ا…
🔧 گوشهای از فعالیتهای موکب خادمالحسین گاهی یک خرابی کوچک خودرو، میتواند خستگی و نگرانی بزرگی برای زائران سیدالشهدا (ع) به همراه داشته باشد؛ اما خادمان امام حسین (ع) آمدهاند تا هیچ زائری در این مسیر احساس تنهایی نکند. به لطف خدا، ماشین مکانیک سیار بهصورت شبانهروزی (۲۴ ساعته) در کنار موکب خادمالحسین (گروه جهادی صاحبالزمان) مستقر شده است تا در صورت بروز هرگونه نقص فنی، در کوتاهترین زمان ممکن به یاری زائران ع…
بسمالله الرحمن الرحیم پس از روزها و ساعتها تلاش، همدلی و کار جهادی، به لطف خداوند متعال و عنایت حضرت اباعبدالله الحسین (ع)، موکب خادمالحسین (گروه جهادی صاحبالزمان (عج)) آماده خدمترسانی به زائران عزیز اربعین حسینی شد. این موکب که در گردنه قلاجه، به عنوان اولین موکب ورودی شهرستان گیلانغرب و دروازه کربلا و چشم گیلانغرب مستقر است، با افتخار از زائران سیدالشهدا (ع) میزبانی خواهد کرد. در این موکب، خدمات صبحانه، ناه…
آغاز عملیات خاکبرداری و تسطیح جایگاه موکب خادمالحسین (گروه جهادی صاحبالزمان (عج)) در گردنه قلاجه، دروازه گیلانغرب به لطف خداوند متعال و با همکاری و حمایت ارزشمند اداره راهداری و حملونقل جادهای شهرستان گیلانغرب، عملیات خاکبرداری و تسطیح جایگاه موکب خادمالحسین (گروه جهادی صاحبالزمان (عج)) مستقر در گردنه قلاجه آغاز شد. این اقدام، گامی مهم در راستای آمادهسازی هرچه بهتر موکب برای خدمترسانی شایسته به زائران حضرت…
Showing the 4 most recent of 4 posts we hold for @tabiat_zagors. 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.
Citation-graph rank — 189,774 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 3 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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“طبیعت زیبای گیلان غرب” (@tabiat_zagors), 273 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/tabiat_zagors.
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.