Telegram RegisterThe public register of Telegram
Telegram profile photo for JaghHub

Channel

JaghHub

@jaghihastiim

On this record: Topic · Observations · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

10,429subscribers

+1,539 since we began measuring on 20 August 2026

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

Register entry

Telegram ID-1002270453472
TypeChannel
Username@jaghihastiim
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live4 November 2026
Measurements held33
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/jaghihastiim

Topic

Film & TV — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Views per post sit far above this size band

11,200 average views per post against 10,429 subscribers — an engagement rate of 107.5%. Across the 52,739 registered channels in the same cohort — 10,001–31,622 subscribers — the middle half sit between 4.11% and 19.3%, with a median of 9.50%.

What this was computed from
Window30 days (5 October 2026 – 4 November 2026)
Posts measured21 of 21 published in the window (0 exact, 21 rounded by Telegram)
Views totalled235,510
Mature posts only111.9% over 20 posts read at least 24h after publication
Subscribers10,429 measured 4 November 2026
Cohortb10000 · 52,739 channels · p10 1.58% · p25 4.11% · p50 9.50% · p75 19.3% · p90 35.1%
Position in cohort99.496th percentile · 11.3× the cohort median
Uncertainty±0.28% of the figure, from Telegram’s rounding

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

Growth

8,89010,4299,659.520 August 2026 — 8,890 subscribers20 August 2026 — 8,890 subscribers20 August 2026 — 8,903 subscribers24 August 2026 — 8,943 subscribers27 August 2026 — 8,949 subscribers31 August 2026 — 9,111 subscribers4 September 2026 — 9,185 subscribers9 September 2026 — 9,275 subscribers13 September 2026 — 9,434 subscribers17 September 2026 — 9,521 subscribers26 September 2026 — 9,813 subscribers5 October 2026 — 9,893 subscribers11 October 2026 — 9,968 subscribers14 October 2026 — 10,024 subscribers15 October 2026 — 10,031 subscribers16 October 2026 — 10,047 subscribers17 October 2026 — 10,076 subscribers19 October 2026 — 10,099 subscribers20 October 2026 — 10,141 subscribers22 October 2026 — 10,181 subscribers23 October 2026 — 10,210 subscribers24 October 2026 — 10,222 subscribers25 October 2026 — 10,227 subscribers26 October 2026 — 10,262 subscribers27 October 2026 — 10,263 subscribers28 October 2026 — 10,321 subscribers29 October 2026 — 10,336 subscribers30 October 2026 — 10,382 subscribers31 October 2026 — 10,385 subscribers1 November 2026 — 10,393 subscribers2 November 2026 — 10,404 subscribers3 November 2026 — 10,400 subscribers4 November 2026 — 10,429 subscribers20 August 20264 November 2026
33 measurements spanning 76 days, net +1,539. 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 8,659–10,660 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
4 Nov 2026, 11:0910,429+29
3 Nov 2026, 10:4010,400-4
2 Nov 2026, 13:0610,404+11
1 Nov 2026, 10:5010,393+8
31 Oct 2026, 13:2910,385+3
30 Oct 2026, 14:1610,382+46
29 Oct 2026, 12:3510,336+15
28 Oct 2026, 11:0510,321+58
27 Oct 2026, 08:2710,263+1
26 Oct 2026, 07:5510,262+35
25 Oct 2026, 06:4610,227+5
24 Oct 2026, 03:1410,222+12
23 Oct 2026, 03:4010,210+29
22 Oct 2026, 03:4710,181+40
20 Oct 2026, 23:4410,141+42
19 Oct 2026, 20:0910,099+23
17 Oct 2026, 16:3110,076+29
16 Oct 2026, 13:2810,047+16
15 Oct 2026, 16:4910,031+7
14 Oct 2026, 16:1010,024first reading

Engagement

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

ERR · 30 days
107.5%
avg views ÷ 10,429 subscribers
Avg views / post
11,200
21 posts measured
Reaction rate
0.324%
reactions ÷ views · ER floor
Posts in window
21
of 60 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 3 November 2026
Posts held60 (12 August 2026 – 3 November 2026)
Views total235,510
Reactions total763
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 08:13 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.

Reaction mix

1,627 reactions across 60 posts, in 10 distinct kinds. The most used accounts for 49.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤80349.4%
👍25615.7%
👎24114.8%
🔥1629.96%
👏633.87%
❤‍🔥493.01%
😍281.72%
🖕150.922%
😁70.43%
🥰30.184%

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

Measured over the 60 most recent posts we hold, published 12 August 2026 to 3 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: 0 of 21 posts held from the last 30 days (0%) 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).

3 Nov 2026, 10:59 UTC≈2,190 views18 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۶

❤9👎9

1 Nov 2026, 18:06 UTC≈4,360 views22 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۵

❤18👍4

31 Oct 2026, 09:44 UTC≈6,310 views49 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۴

🔥19👏17👎8❤4👍1

29 Oct 2026, 21:02 UTC≈8,590 views36 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۳

❤19👎15👍2

29 Oct 2026, 21:00 UTC≈8,600 views19 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۲

❤14👍5

29 Oct 2026, 20:59 UTC≈8,620 views30 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۱

🔥23❤6👍1

29 Oct 2026, 20:23 UTC≈8,680 views39 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۹

👎25❤‍🔥12🥰2

29 Oct 2026, 20:22 UTC≈8,620 views42 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۸

👎23❤‍🔥17❤2

29 Oct 2026, 20:21 UTC≈8,580 views38 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۷

👎21❤‍🔥17

29 Oct 2026, 20:20 UTC≈8,560 views42 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۶

👎20❤19❤‍🔥2👍1

28 Oct 2026, 07:37 UTC≈10,700 views46 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 ۵

👍21❤19👎6

27 Oct 2026, 14:01 UTC≈11,500 views37 reactionsread 4 November 2026

🇮🇷 دانلود فیلم 🇮🇷 4

👍19❤16👎2

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

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.

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

“JaghHub” (@jaghihastiim), 10,429 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/jaghihastiim.

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.