Channel
@mehrellahi
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
69subscribers
-5 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003340954126 |
|---|---|
| Type | Channel |
| Username | @mehrellahi |
| Created | Between 1 November 2025 and 24 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 6 times, most recently 11 November 2026 |
| On Telegram | t.me/mehrellahi |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @mehrellahi/41 · this entry3 Jun 2026, 09:49 UTC | @safarnor1/493 Jun 2026, 09:50 UTC | 1.00 | under a minute |
| @safarnor1/548 Jun 2026, 08:18 UTC | @mehrellahi/45 · this entry8 Jun 2026, 08:18 UTC | 1.00 | under a minute |
| @safarnor1/5920 Jun 2026, 20:24 UTC | @mehrellahi/50 · this entry20 Jun 2026, 20:24 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @safarnor1 | 11 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (6–5) |
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. None of the 3 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 25 February 2026 to 8 July 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @safarnor1. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 11 November 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.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 14:00 | 69 | -1 |
| 18 Sept 2026, 16:40 | 70 | -1 |
| 9 Sept 2026, 16:36 | 71 | -1 |
| 1 Sept 2026, 04:05 | 72 | -1 |
| 16 Aug 2026, 04:04 | 73 | -1 |
| 9 Aug 2026, 21:47 | 74 | no change |
| 8 Aug 2026, 22:46 | 74 | first reading |
20 posts held, back to 24 February 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 8 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 10 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.
🛑 در ابر رویداد تاریخ معاصر چه گذشت؟/ از حضور ۱۰۰ هیات دیپلماتیک تا اجتماعهای میلیونی وداع و بدرقه/ جهان نظاره گر انسجام ملی و اقتدار امنیتی 🔹️ ابر رویداد تاریخ معاصر ایران که بیش از ۹۰ ساعت به طول انجامید با ورود هیاتهای دیپلماتیک از مقامات ۱۰۰ کشور جهان آغاز شد. 🔹️حضور میلیونها عزادار با اندوه، خشم و حماسه در مصلای بزرگ تهران برای وداع با آقای شهید و خونخواهی قاعد امت، جلوه های خیره کننده ای از انسجام ملی را از …
🛑 در ابر رویداد تاریخ معاصر چه گذشت؟/ از حضور ۱۰۰ هیات دیپلماتیک تا اجتماعهای میلیونی وداع و بدرقه/ جهان نظاره گر انسجام ملی و اقتدار امنیتی 🔹️ ابر رویداد تاریخ معاصر ایران که بیش از ۹۰ ساعت به طول انجامید با ورود هیاتهای دیپلماتیک از مقامات ۱۰۰ کشور جهان آغاز شد. 🔹️حضور میلیونها عزادار با اندوه، خشم و حماسه در مصلای بزرگ تهران برای وداع با آقای شهید و خونخواهی قاعد امت، جلوه های خیره کننده ای از انسجام ملی را از …
🎥 #بگو_همه_بخونن... 🔹️ کاربران شبکه های اجتماعی با هشتگ #بگو_همه_بخونن برای اقامه نماز بر پیکر مطهر رهبر شهید انقلاب و خانواده ایشان آماده می شوند... 🔹️ این نماز اوایل صبح فردا اقامه می شود @baseeratt
🔻نقشه راه حضور در مصلای تهران برای مراسم وداع با پیکر رهبر شهید انقلاب @TehranNewsir
مسیرهای دسترسی از جنوب تهران به مراسم بدرقه رهبر شهید انقلاب 🔹معاونت حملونقل و ترافیک شهرداری تهران با انتشار موشنگرافی، مسیرهای دسترسی خودروهای ورودی از جنوب تهران به مراسم بدرقه رهبر شهید انقلاب را تشریح کرد. 🔹هموطنانی که قصد دارند از مسیر جنوب تهران خود را به محل برگزاری مراسم بدرقه رهبر شهید انقلاب برسانند، میتوانند مسیرهای پیشنهادی را مشاهده و بر اساس آن تردد کنند. @TehranNewsir
🏴عاشقان امام شهید بسمالله 🔻برپایی موکب خدمت رسانی به زائران امام شهید در مصلی تهران ⏰زمان: روزهای ۱۳ و ۱۴ تیرماه هم زمان با تشییع امام خامنهای 😭 📢علاقمندان به خادمی در موکب امام شهید میتوانن از طریق لینک زیر ثبت نام نمایند. https://survey.porsline.ir/s/dhntAxKb #نشر_حداکثری 🏴موکب الشهداء شهرستان قرچک @mokeb_shohada1445
رفع مشکل خیابان ۲۰ متری نواب صفوی نسیمشهر 🔹 پس از انتشار مطالبه یکی از شهروندان نسیمشهری درباره حفاریهای ناایمن و وضعیت خطرناک خیابان ۲۰ متری نواب صفوی در محله خیرآباد که در پی اجرای پروژه فیبر نوری ایجاد شده بود، شهرداری وارد عمل شد و این معبر ایمنسازی شد. 🔹 این شهروند پیشتر با ارسال پیامی به «تهران نیوز»، نسبت به تبدیل شدن این خیابان به محل حادثه برای راکبان موتور و دوچرخه اعتراض کرده و خواستار ورود فوری مسئ…
وقتی یک نام، فراتر از مرزها میشود، فاصلهها رنگ میبازند… این تشییع، تنها بدرقه یک شهید نیست؛ نمایش شکوه یک امت و اقتدار یک آرمان است.🖤🥀 @Baseeratt
اولین سالگرد عروج سردار شهید حسین سلامی در حرم حضرت عبدالعظیم حسنی (ع) برگزار خواهد شد
✍️🇮🇷 وقتی از ایران مینویسیم، از غیرت، ایمان و نام علی (ع) مینویسیم. #ایران_یعنی_دیار_علی
🎉 جشن بزرگ خیابانی عید غدیر در شهرستان دماوند خیابانهای دماوند غرق در شور و شادی ولایت شد؛ از لبخند کودکان تا حضور پرشور خانوادهها، همه آمده بودند تا عشق خود را به مولای متقیان حضرت علی (ع) فریاد بزنند. غدیر؛ عید وحدت، محبت و ولایت.
💚 جشن باشکوه عید سعید غدیر در مسجدالنبی شبی سرشار از شور ولایت، لبخند کودکان، نوای شادی مؤمنان و تجدید عهد با امیرالمؤمنین حضرت علی (ع). غدیر تنها یک روز نیست؛ آغاز راهی است که به روشنایی و هدایت ختم میشود.
Showing the 12 most recent of 20 posts we hold for @mehrellahi. 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.
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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“مهر الهی🌼” (@mehrellahi), 69 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/mehrellahi.
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.