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.
Views per post sit far above this size band
8,210 average views per post against 11,103 subscribers — an engagement rate of 73.9%. Across the 8,206 registered channels in the same cohort — 10,002–31,604 subscribers, posting mainly in Persian — the middle half sit between 3.63% and 17.0%, with a median of 8.56%.
What this was computed from
Window
30 days (21 July 2026 – 20 August 2026)
Posts measured
38 of 38 published in the window (0 exact, 38 rounded by Telegram)
Views totalled
311,880
Mature posts only
75.9% over 36 posts read at least 24h after publication
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 20 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.
Growth
14 measurements spanning 14 days, net +846. 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 9,970–11,251 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
21 Aug 2026, 08:02
10,964
-139
20 Aug 2026, 10:13
11,103
+75
19 Aug 2026, 12:52
11,028
+117
18 Aug 2026, 09:42
10,911
+22
17 Aug 2026, 10:02
10,889
+68
15 Aug 2026, 20:07
10,821
+417
14 Aug 2026, 10:34
10,404
+63
13 Aug 2026, 01:47
10,341
+132
12 Aug 2026, 02:14
10,209
+26
11 Aug 2026, 02:31
10,183
+27
9 Aug 2026, 23:35
10,156
+17
9 Aug 2026, 01:10
10,139
+21
7 Aug 2026, 19:47
10,118
no change
7 Aug 2026, 19:34
10,118
first reading
Engagement
39 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 25 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
76.9%
avg views ÷ 10,964 subscribers
Avg views / post
8,440
39 posts measured
Reaction rate
2.72%
reactions ÷ views · ER floor
Posts in window
39
of 39 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
Window
Rolling 30 days · latest post in window 20 August 2026
Posts held
39 (5 August 2026 – 20 August 2026)
Views total
328,990
Reactions total
8,956
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Aug 2026, 15:26 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
327
Videos
22
Links
37
Lifetime counters from Telegram’s own channel header, read 22 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
8,956 reactions across 39 posts, in 26 distinct kinds. The most used accounts for 60.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
5,406
60.4%
😁
606
6.77%
👍
539
6.02%
👎
477
5.33%
❤🔥
344
3.84%
🍓
287
3.20%
😭
259
2.89%
😍
255
2.85%
🔥
243
2.71%
💔
159
1.78%
💘
120
1.34%
🍾
60
0.67%
💯
39
0.435%
🕊
37
0.413%
🤩
32
0.357%
👀
31
0.346%
🌚
16
0.179%
☃
14
0.156%
🆒
7
0.078%
🤓
7
0.078%
6 further kinds
18
0.201%
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 39 of the 39 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 8,956reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 39 most recent posts we hold, published 5 August 2026 to 20 August 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.
Showing the 12 most recent of 39 posts we hold for @farnaz_hsz. 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 — 342,490 of 1,583,249entries 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.
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.
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 21 August 2026 — this
entry's latest reading, not the date you are reading this.
“فرناز حسن زاده | رتبه یک کنکور ۱۴۰۱” (@farnaz_hsz), 10,964 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/farnaz_hsz.
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.
