Telegram RegisterThe public register of Telegram

Channel

Mehraz Logs

@Mehraz_Logs

On this record: Growth · Engagement · Posts · Citations · Cite this entry

426subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002438820540
TypeChannel
Username@Mehraz_Logs
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Mehraz_Logs

Growth

4264284277 August 2026 — 428 subscribers7 August 2026 — 428 subscribers14 August 2026 — 426 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net -2. 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 426–428 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:49426-2
7 Aug 2026, 04:00428no change
7 Aug 2026, 03:48428first reading

Engagement

20 posts held, back to 26 July 2026the 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 · 30 days
31.0%
avg views ÷ 426 subscribers
Avg views / post
132
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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 6 August 2026
Posts held20 (26 July 20266 August 2026)
Views total2,645
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 04:00 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.

Recent posts

6 Aug 2026, 06:26 UTC43 viewsread 7 August 2026

https://nerve.news/wires/iran-linked-cyberattacks-target-water-systems-across-12-states-1785976402760 #news

6 Aug 2026, 06:24 UTC44 viewsread 7 August 2026

https://www.jfeed.com/news-israel/iran-espionage-israel-satmar #news

6 Aug 2026, 06:21 UTC42 viewsread 7 August 2026

AI data centers have become sitting ducks in the Iran war #news

2 Aug 2026, 16:05 UTC127 viewsread 7 August 2026

Implications of Recent CISA Disclosures on Iranian OT System Targeting #news

31 Jul 2026, 19:33 UTC196 viewsread 7 August 2026

https://exclusive.iranintl.com/amir-barati-iranian-hacker-fbi-trap/ #news

31 Jul 2026, 15:21 UTC161 viewsread 7 August 2026

Illicit Iranian gambling network helped pull off a $4 billion sanctions dodge #news

30 Jul 2026, 19:45 UTC175 viewsread 7 August 2026

Iran War’s Secondary Effects Shape 2026 US Violent Extremism #news

30 Jul 2026, 19:12 UTC164 viewsread 7 August 2026

Iranian Hackers Exploited Unpatchable PLC Flaw to Breach 30 Minnesota Water Systems #news

30 Jul 2026, 18:52 UTC154 viewsread 7 August 2026

VPN Breach Exposes 58 Million Connection Logs Despite “No-Logs” Claims #news #privacy

30 Jul 2026, 18:41 UTC151 viewsread 7 August 2026

China, Russia, Iran and North Korea form 'axis of aggressors' that could overwhelm US, book warns #news #book

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

Citation-graph rank — 955,386 of 1,345,403entries 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.

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

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

“Mehraz Logs” (@Mehraz_Logs), 426 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Mehraz_Logs.

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.