Telegram RegisterThe public register of Telegram
Telegram profile photo for هواداران سپاهان

Channel

هواداران سپاهان

@sepahanfcofficial

On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry

7,932subscribers

-626 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001000680228
TypeChannel
Username@sepahanfcofficial
CreatedBetween 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/sepahanfcofficial

Topic

Sports — 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 12 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 why it has no browse page of its own yet.

Previous handles

Recorded in 2019 as “کانال هواداران سپاهان — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.

Growth

7,9328,5588,2455 August 2026 — 8,558 subscribers6 August 2026 — 8,540 subscribers6 August 2026 — 8,540 subscribers8 August 2026 — 8,244 subscribers11 August 2026 — 8,176 subscribers14 August 2026 — 8,133 subscribers17 August 2026 — 8,107 subscribers21 August 2026 — 8,091 subscribers24 August 2026 — 8,079 subscribers27 August 2026 — 8,068 subscribers30 August 2026 — 8,056 subscribers3 September 2026 — 8,015 subscribers8 September 2026 — 7,982 subscribers12 September 2026 — 7,959 subscribers16 September 2026 — 7,932 subscribers5 August 202616 September 2026
15 measurements spanning 42 days, net -626. 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 7,838–8,652 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 14:207,932-27
12 Sept 2026, 15:377,959-23
8 Sept 2026, 12:017,982-33
3 Sept 2026, 06:258,015-41
30 Aug 2026, 19:188,056-12
27 Aug 2026, 18:458,068-11
24 Aug 2026, 22:498,079-12
21 Aug 2026, 02:538,091-16
17 Aug 2026, 18:198,107-26
14 Aug 2026, 15:078,133-43
11 Aug 2026, 15:428,176-68
8 Aug 2026, 18:438,244-296
6 Aug 2026, 03:028,540no change
6 Aug 2026, 00:458,540-18
5 Aug 2026, 18:548,558first reading

Engagement

133 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.4%
avg views ÷ 7,932 subscribers
Avg views / post
824
42 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
42
of 133 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 28 August 2026
Posts held133 (2 August 202628 August 2026)
Views total34,594
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 19:04 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

Video runtime
46m 48s
Average length
1m 28s

Measured directly from 32 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.

Recent posts

28 Aug 2026, 18:18 UTC218 viewsread 28 August 2026
Photo

💛 گل شماره 1100 سپاهان در تاریخ لیگ‌برتر با بریس کسری طاهری ثبت شد. ⁨📲 instagram: https://instagram.com/sepahanfcofficial #هواداران_سپاهان ↙️ 🆔 @SepahanFcOfficial

28 Aug 2026, 18:02 UTC335 viewsread 28 August 2026
Photo

💛 FULL-TIME سپاهان 2 گل گهر 0 ⁨📲 instagram: https://instagram.com/sepahanfcofficial #هواداران_سپاهان ↙️ 🆔 @SepahanFcOfficial

28 Aug 2026, 17:50 UTC401 viewsread 28 August 2026
Photo

💛 دقیقه 90| تعویض پنجم برای سپاهان 🟡 هادی محمدی به جای حاج صفی وارد زمین شد 📲 instagram: https://instagram.com/sepahanfcofficial #هواداران_سپاهان ↙️ 🆔 @SepahanFcOfficial

28 Aug 2026, 17:45 UTC415 viewsread 28 August 2026
Photo

💛 دقیقه 84| تعویض سوم و چهارم برای سپاهان 🟡 نورافکن و جلالی وند به جای لطفی و رضاوند وارد زمین شدند 📲 instagram: https://instagram.com/sepahanfcofficial #هواداران_سپاهان ↙️ 🆔 @SepahanFcOfficial

28 Aug 2026, 17:37 UTC450 viewsread 28 August 2026
Photo

💛 دقیقه 75| تعویض دوم برای سپاهان 🟡 ثابت ایمانی به جای حبیبی وارد زمین شد 📲 instagram: https://instagram.com/sepahanfcofficial #هواداران_سپاهان ↙️ 🆔 @SepahanFcOfficial

28 Aug 2026, 17:09 UTC529 viewsread 28 August 2026

کسری طاهری به علت مصدومیت تعویض شد

28 Aug 2026, 17:07 UTC535 viewsread 28 August 2026
Photo

💛 دقیقه 46| تعویض اول برای سپاهان 🟡 کاوه رضایی به جای کسری طاهری وارد زمین شد 📲 instagram: https://instagram.com/sepahanfcofficial #هواداران_سپاهان ↙️ 🆔 @SepahanFcOfficial

28 Aug 2026, 16:48 UTC579 viewsread 28 August 2026

💛 پایان نیمه اول 🟡 سپاهان 2️⃣ گل گهر 0️⃣ 📲 instagram: https://instagram.com/sepahanfcofficial #هواداران_سپاهان ↙️ 🆔 @SepahanFcOfficial

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

هواداران سپاهان
@SEPAHAN · 23,147
Telegram ranks this channel #23 of 89 here — alongside 88 others — read 19 September 2026
آخرین خبر اصفهان
@Isfahan_today · 26,335
Telegram ranks this channel #31 of 81 here — alongside 80 others — read 12 September 2026
■ کانال اصفهانی ها ■
@isf031 · 137,642
Telegram ranks this channel #50 of 60 here — alongside 59 others — read 13 August 2026
عجایب جهان!
@AjayebeNews · 22,474
Telegram ranks this channel #61 of 61 here — alongside 60 others — read 20 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“هواداران سپاهان” (@sepahanfcofficial), 7,932 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/sepahanfcofficial.

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.