Telegram RegisterThe public register of Telegram
Telegram profile photo for میهن نیوز | خبر جنگ فوری

Channel

میهن نیوز | خبر جنگ فوری

@revayatemihan

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

7,162subscribers

-11,655 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003276751847
TypeChannel
Username@revayatemihan
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held45
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/revayatemihan

Topic

International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 85% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@withyashar/206156 Aug 2026, 20:32 UTC@revayatemihan/1490 · this entry7 Aug 2026, 09:25 UTC0.9713 hours
@withyashar/206186 Aug 2026, 20:57 UTC@revayatemihan/1484 · this entry7 Aug 2026, 08:51 UTC0.9712 hours
@withyashar/206277 Aug 2026, 08:02 UTC@revayatemihan/1489 · this entry7 Aug 2026, 08:59 UTC0.9757 minutes
@withyashar/206166 Aug 2026, 20:34 UTC@revayatemihan/1491 · this entry7 Aug 2026, 09:29 UTC0.9513 hours
@withyashar/206567 Aug 2026, 18:02 UTC@revayatemihan/1514 · this entry7 Aug 2026, 19:12 UTC0.9470 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@withyashar5 (5/5 hand-verifiable sample passed)0.967.2 hours@withyashar (5–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 41 comparable posts for this entry, running 5 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @withyashar. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

7,16218,81712,989.56 August 2026 — 18,817 subscribers6 August 2026 — 18,673 subscribers7 August 2026 — 18,337 subscribers8 August 2026 — 17,667 subscribers9 August 2026 — 17,308 subscribers10 August 2026 — 17,111 subscribers11 August 2026 — 16,535 subscribers12 August 2026 — 16,166 subscribers13 August 2026 — 15,958 subscribers14 August 2026 — 15,635 subscribers16 August 2026 — 15,016 subscribers17 August 2026 — 14,641 subscribers18 August 2026 — 14,209 subscribers19 August 2026 — 14,042 subscribers20 August 2026 — 13,929 subscribers21 August 2026 — 13,835 subscribers22 August 2026 — 13,564 subscribers24 August 2026 — 13,438 subscribers25 August 2026 — 13,302 subscribers26 August 2026 — 13,180 subscribers27 August 2026 — 13,108 subscribers28 August 2026 — 12,876 subscribers29 August 2026 — 12,479 subscribers31 August 2026 — 12,229 subscribers1 September 2026 — 12,014 subscribers2 September 2026 — 11,866 subscribers3 September 2026 — 11,532 subscribers5 September 2026 — 11,373 subscribers8 September 2026 — 11,029 subscribers11 September 2026 — 10,782 subscribers13 September 2026 — 10,145 subscribers14 September 2026 — 9,641 subscribers18 September 2026 — 9,058 subscribers28 September 2026 — 8,419 subscribers5 October 2026 — 8,150 subscribers12 October 2026 — 7,941 subscribers15 October 2026 — 7,716 subscribers18 October 2026 — 7,626 subscribers20 October 2026 — 7,548 subscribers23 October 2026 — 7,465 subscribers26 October 2026 — 7,415 subscribers29 October 2026 — 7,356 subscribers1 November 2026 — 7,273 subscribers4 November 2026 — 7,231 subscribers7 November 2026 — 7,162 subscribers6 August 20267 November 2026
45 measurements spanning 93 days, net -11,655. 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”. The vertical axis spans 5,414–20,565 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)SubscribersChange
7 Nov 2026, 13:207,162-69
4 Nov 2026, 10:157,231-42
1 Nov 2026, 19:297,273-83
29 Oct 2026, 08:417,356-59
26 Oct 2026, 15:167,415-50
23 Oct 2026, 21:067,465-83
20 Oct 2026, 21:507,548-78
18 Oct 2026, 04:297,626-90
15 Oct 2026, 09:267,716-225
12 Oct 2026, 11:427,941-209
5 Oct 2026, 16:578,150-269
28 Sept 2026, 05:388,419-639
18 Sept 2026, 13:589,058-583
14 Sept 2026, 16:219,641-504
13 Sept 2026, 05:1610,145-637
11 Sept 2026, 05:3610,782-247
8 Sept 2026, 10:5811,029-344
5 Sept 2026, 04:3711,373-159
3 Sept 2026, 10:4211,532-334
2 Sept 2026, 05:1611,866first reading

Engagement

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

ERR · 30 days
0.455%
avg views ÷ 7,162 subscribers
Avg views / post
32.6
208 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
208
of 840 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. It is computed over the 1 of 208 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 November 2026
Posts held840 (5 August 2026 – 8 November 2026)
Views total6,780
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 20:07 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

Photos
≈1,660
Videos
≈1,230
Links
≈10

Lifetime counters from Telegram’s own channel header, read 8 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1h 45m
Average length
42s

Measured directly from 151 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

52 reactions across 41 posts, in 14 distinct kinds. The most used accounts for 19.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1019.2%
👎917.3%
❤713.5%
💩47.69%
👏35.77%
🔥35.77%
🖕35.77%
😁35.77%
🤣35.77%
🤮35.77%
💔11.92%
🤡11.92%
🤬11.92%
🥴11.92%

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

Measured over the 840 most recent posts we hold, published 5 August 2026 to 8 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.

Recent posts

Telegram’s own ‘edited’ marker: 45 of 208 posts held from the last 30 days (21.6%) 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).

8 Nov 2026, 19:20 UTC27 viewsread 8 November 2026

🐖ترامپ : اگر مذاکرات به خوبی پیش برود، «بسیار بعید است» ایالات متحده دوباره وارد جنگ شود آمریکا می‌تواند ظرف یک ساعت ۳۸ پل ایران را منهدم کند ایران تنها ۱۰ درصد از توان موشکی و ۱۵ درصد از توان پهپادی خود را در اختیار دارد @revayatemihan

8 Nov 2026, 19:19 UTC31 viewsread 8 November 2026

گزارش انفجار بندر عباس @revayatemihan 🚨🚨🚨🚨

8 Nov 2026, 19:19 UTC33 viewsread 8 November 2026

کانال 14 اسراییل: عراقچی به آمریکا گفته جنگ را انتخاب کنید تا جهنم بر سرتان فرود آید @revayatemihan

8 Nov 2026, 19:18 UTC35 viewsread 8 November 2026

۶ انفجار سنگین قشم 🚨🚨🚨🚨🚨🚨 @revayatemihan

8 Nov 2026, 19:18 UTC34 viewsread 8 November 2026

دیدبان اتاق جنگ : پدافند قشم رو زدن @revayatemihan🚨🚨🚨🚨

8 Nov 2026, 19:17 UTC32 viewsread 8 November 2026

⭕️آخرین پیشنهاد گزارش‌شده قطر: غنی‌سازی ۳٫۶۷ درصدی ایران (با تضمین عاصم منیر)، رقیق‌سازی ۴۰۰ کیلوگرم اورانیوم ۶۰ درصدی در ایران رفع محاصره دریایی ایران از سوی آمریکا، آزادسازی ۶ تا ۱۰ میلیارد دلار میانجی‌گری ایران میان عربستان سعودی و حوثی‌ها اجازه ورود به بازرسان آژانس بین‌المللی انرژی اتمی و سپس بازگشایی تنگه. (به نقل از یک «روزنامه‌نگار» وابسته به دولت 🔈@revayatemihan

8 Nov 2026, 19:17 UTC28 viewsread 8 November 2026

🔴 یک انفجار در تنگه هرمز. 🔈@revayatemihan

8 Nov 2026, 19:17 UTC27 viewsread 8 November 2026

⭕️کانال 13 اسرائیل: فرمانده سنتکام به ارتش اسرائیل اطلاع داده است که هرگونه حمله جدید علیه ایران، هدف آن زیرساخت‌ها از جمله پل‌ها و نیروگاه‌ها خواهد بود @revayatemihan

8 Nov 2026, 19:17 UTC25 viewsread 8 November 2026

⭕️کانال 13 اسرائیل فرمانده سنتکام به فرماندهان ارتش اسرائیل اطلاع داده است که می‌توان حملات جدید مشترکی علیه ایران انجام داد 🔈@revayatemihan

8 Nov 2026, 19:17 UTC26 viewsread 8 November 2026

💢گزارش شنیده شدن صدای انفجار بندر ماهشهر 🔈@revayatemihan

8 Nov 2026, 19:17 UTC26 viewsread 8 November 2026

‼️⭕️شبکه i24 نیوز: با این حال ترامپ به معاون رئیس‌جمهور، جِی. دی. ونس، و مقامات ارشد دولت خود چندین روز دیگر فرصت داده است تا تلاش‌های دیپلماتیک خود را با ایران به پایان برسانند و در صورت عدم دستیابی به توافقی با ایران در روز های آینده جنگ آغاز خواهد شد. 🔈@revayatemihan

8 Nov 2026, 19:17 UTC19 viewsread 8 November 2026

‼️⭕️شبکه i24 نیوز: اسرائیل برای احتمال دستور حمله ترامپ علیه ایران در طول 48 ساعت گذشته آمادگی داشت،این موضوع باعث شد که نتانیاهو روز جمعه پس از تماس تلفنی با ترامپ،جلسه‌ای فوق العاده با مقامات ارشد امنیتی برگزار کند. 🔈@revayatemihan

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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 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.

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

“میهن نیوز | خبر جنگ فوری” (@revayatemihan), 7,162 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/revayatemihan.

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.