Telegram RegisterThe public register of Telegram
Telegram profile photo for ایـران دیده بان

Channel

ایـران دیده بان

@IRAN_DIDEHBAN

2 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

12,403subscribers

+7,379 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003811552009
TypeChannel
Usernames@IRAN_DIDEHBAN @IRANDIDEBAN1
CreatedBetween 1 February 2026 and 30 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held47
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/IRAN_DIDEHBAN

Topic

National news — 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 98% 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.

Growth

312,4036,2037 August 2026 — 5,024 subscribers7 August 2026 — 5,024 subscribers8 August 2026 — 5,020 subscribers10 August 2026 — 5,000 subscribers13 August 2026 — 4,982 subscribers16 August 2026 — 4,969 subscribers20 August 2026 — 4,951 subscribers23 August 2026 — 4,917 subscribers26 August 2026 — 4,898 subscribers29 August 2026 — 4,872 subscribers1 September 2026 — 5,231 subscribers5 September 2026 — 5,632 subscribers10 September 2026 — 5,926 subscribers14 September 2026 — 6,080 subscribers15 September 2026 — 6,392 subscribers16 September 2026 — 6,460 subscribers19 September 2026 — 3 subscribers24 September 2026 — 6,885 subscribers4 October 2026 — 4 subscribers4 October 2026 — 7,229 subscribers11 October 2026 — 7,498 subscribers13 October 2026 — 5 subscribers14 October 2026 — 8,412 subscribers17 October 2026 — 8,830 subscribers20 October 2026 — 7 subscribers21 October 2026 — 8,954 subscribers24 October 2026 — 9,420 subscribers26 October 2026 — 10,042 subscribers27 October 2026 — 13 subscribers27 October 2026 — 10,067 subscribers28 October 2026 — 10,060 subscribers30 October 2026 — 10,067 subscribers31 October 2026 — 10,063 subscribers1 November 2026 — 10,160 subscribers2 November 2026 — 10,177 subscribers3 November 2026 — 10,681 subscribers3 November 2026 — 291 subscribers4 November 2026 — 10,890 subscribers5 November 2026 — 10,968 subscribers6 November 2026 — 10,988 subscribers7 November 2026 — 11,388 subscribers8 November 2026 — 11,809 subscribers9 November 2026 — 11,848 subscribers11 November 2026 — 326 subscribers11 November 2026 — 11,854 subscribers13 November 2026 — 11,863 subscribers17 November 2026 — 12,403 subscribers7 August 202617 November 2026
47 measurements spanning 101 days, net +7,379. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
17 Nov 2026, 00:5012,403+540
13 Nov 2026, 20:4511,863+9
11 Nov 2026, 02:0911,854+11,528
11 Nov 2026, 01:58326-11,522
9 Nov 2026, 14:3711,848+39
8 Nov 2026, 04:1911,809+421
7 Nov 2026, 00:5411,388+400
6 Nov 2026, 02:1910,988+20
5 Nov 2026, 04:3110,968+78
4 Nov 2026, 04:0910,890+10,599
3 Nov 2026, 04:38291-10,390
3 Nov 2026, 00:4610,681+504
2 Nov 2026, 02:2810,177+17
1 Nov 2026, 00:0510,160+97
31 Oct 2026, 02:5810,063-4
30 Oct 2026, 02:5010,067+7
28 Oct 2026, 23:3610,060-7
27 Oct 2026, 20:4110,067+10,054
27 Oct 2026, 20:3113-10,029
26 Oct 2026, 17:4410,042first reading

Engagement

323 posts held, back to 30 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 33 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
45.6%
avg views ÷ 12,403 subscribers
Avg views / post
5,660
278 posts measured
Reaction rate
1.81%
reactions ÷ views · ER floor
Posts in window
278
of 323 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held323 (30 July 2026 – 16 November 2026)
Views total1,573,686
Reactions total28,439
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 21:53 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.

What this channel posts

Video runtime
7m 41s
Average length
18s

Measured directly from 26 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.

Reaction mix

31,016 reactions across 323 posts, in 7 distinct kinds. The most used accounts for 31.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬9,73331.4%
🔥7,13223.0%
❤6,51621.0%
👍2,9999.67%
🤯2,3987.73%
💔1,5014.84%
👎7372.38%

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 323 of the 323 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 31,016 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 323 most recent posts we hold, published 30 July 2026 to 16 November 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 Stars

Stars received
6
across the posts below
Posts paid on
4
of 323 we hold a reading for · 1%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @IRAN_DIDEHBAN. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 323 most recent posts we hold for this entry, published 30 July 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 11 of 278 posts held from the last 30 days (3.96%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 21:29 UTC≈1,400 views74 reactionsread 16 November 2026

این پهپاد منهدم نشده و سالم دست نیروها افتاده است؛ این را هم کپی کنید. 🆔 @IRAN_DIDEHBAN

🔥61❤7👍5🤯1

16 Nov 2026, 21:29 UTC≈1,400 views26 reactionsread 16 November 2026
Photo

کانال های کپی کار ... 🆔 @IRAN_DIDEHBAN

👍23🤬3

16 Nov 2026, 21:23 UTC≈1,680 views28 reactionsread 16 November 2026

🚫انهدام یک پهپاد دیگر 🆔 @IRAN_DIDEHBAN

❤28

16 Nov 2026, 21:21 UTC≈1,810 views11 reactionsread 16 November 2026

تحرکات شناسایی رژیم برای تهران؟ در کانال همسایه

🔥8👍3

16 Nov 2026, 20:50 UTC≈2,670 views72 reactionsread 16 November 2026

🚨دقایقی قبل یک نفتکش متخلف که با خاموش کردن سامانه‌های ناوبری در منطقه ممنوعه شرق تنگه هرمز تردد می‌کرد، بر اثر برخورد با مین دریایی دچار حریق شد و شدیداً آسیب دید. 🆔 @IRAN_DIDEHBAN

👍58❤8🔥3🤯2🤬1

16 Nov 2026, 20:28 UTC≈3,760 views56 reactionsread 16 November 2026

📡 جمع بندی گزارش ها به سامانه ایران دیده بان در روزهای گذشته: ⏺پرواز های شناسایی دشمن به شدت افزایش پیدا کرده است. 🚫پهپاد های دشمن در حریم هوایی ساحل شمال کشور و همچنین شمال غرب بارها مشاهده و گزارش شدند. ⏺ به نظر می رسد چند سری از پهپادهای اوربیتر متعلق به اسرائیل، بیش از چندبار موفق به ورود به حریم هوایی کشور شده و همچنین دائما بر کریدور نیمه ثابت رژیم برای بمباران تهران و مرکز کشور، نظارت می کنند. 🚫تعداد قابل…

❤43👍6🔥3💔2🤬2

16 Nov 2026, 19:15 UTC≈4,720 views146 reactionsread 16 November 2026

🇺🇸🚨 اکنون سنت‌کام رسماً اعلام می‌کند: ناو هواپیمابر روزولت به منطقه فرماندهی مرکزی ایالات متحده رسیده است. 🆔 @IRAN_DIDEHBAN

🤬118🔥18❤3👎3🤯3👍1

16 Nov 2026, 18:29 UTC≈5,130 views76 reactionsread 16 November 2026

وبحسب ما ورد، أصدرت الحكومة العراقية إنذاراً نهائياً لميليشيات كتائب حزب الله المدعومة من إيران، تطلب منها نزع سلاحها والانسحاب من قاعدتها في جرف الصخر أو مواجهة عمل عسكري. @IRANDIDEBAN1 | الرَّصَدُ الإيرانيّ

🤬60🔥8❤7👍1

16 Nov 2026, 18:15 UTC≈5,390 views70 reactionsread 16 November 2026

فعالیت هواپیماهای جنگنده بر فراز مرکز اسرائیل. 🆔 @IRAN_DIDEHBAN

❤35🤬33🔥1🤯1

16 Nov 2026, 17:49 UTC≈5,940 views92 reactionsread 16 November 2026

تایید شد. فعال شدن پدافند هوایی در اصفهان 🆔 @IRAN_DIDEHBAN

🤯78❤7🤬4🔥3

16 Nov 2026, 17:49 UTC≈5,730 views79 reactionsread 16 November 2026

گزارش فعالیت فشرده پدافند هوایی در رامهرمز 🆔 @IRAN_DIDEHBAN

🔥61🤯10❤6🤬2

16 Nov 2026, 17:27 UTC≈5,960 views166 reactionsread 16 November 2026
Video

انتشار برای نخستین بار 🔹‌لحظه انهدام جنگنده f15 متجاوز آمریکایی 🆔 @IRAN_DIDEHBAN

❤123🔥29👎14

Showing the 12 most recent of 323 posts we hold for @IRAN_DIDEHBAN. 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.

Posts edited after publishing

@IRAN_DIDEHBAN edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
4 November 2026
Most recent edit
11 November 2026

Forward network

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.

Mentions

Named by 11 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.

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.

Cite this entry

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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“ایـران دیده بان” (@IRAN_DIDEHBAN), 12,403 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/IRAN_DIDEHBAN.

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.