Telegram RegisterThe public register of Telegram
Telegram profile photo for Persian Cinema Club

Channel

Persian Cinema Club

@PersianCinemaClub

On this record: Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

31,366subscribers

+6,280 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001155188659
TypeChannel
Username@PersianCinemaClub
CreatedBetween 1 February 2019 and 30 September 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live8 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/PersianCinemaClub

Growth

25,08631,36628,2266 August 2026 — 25,086 subscribers6 August 2026 — 25,093 subscribers7 August 2026 — 25,104 subscribers8 August 2026 — 25,115 subscribers9 August 2026 — 25,122 subscribers10 August 2026 — 25,200 subscribers11 August 2026 — 25,293 subscribers12 August 2026 — 25,367 subscribers13 August 2026 — 25,418 subscribers14 August 2026 — 25,493 subscribers15 August 2026 — 25,493 subscribers16 August 2026 — 25,696 subscribers17 August 2026 — 27,840 subscribers18 August 2026 — 28,650 subscribers19 August 2026 — 28,767 subscribers20 August 2026 — 28,890 subscribers21 August 2026 — 28,939 subscribers23 August 2026 — 28,965 subscribers24 August 2026 — 28,954 subscribers25 August 2026 — 28,957 subscribers26 August 2026 — 28,959 subscribers27 August 2026 — 28,968 subscribers28 August 2026 — 28,973 subscribers29 August 2026 — 28,962 subscribers31 August 2026 — 28,966 subscribers1 September 2026 — 29,133 subscribers2 September 2026 — 29,405 subscribers3 September 2026 — 29,443 subscribers5 September 2026 — 30,916 subscribers8 September 2026 — 31,366 subscribers6 August 20268 September 2026
30 measurements spanning 33 days, net +6,280. 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 24,144–32,308 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
8 Sept 2026, 09:2131,366+450
5 Sept 2026, 07:3930,916+1,473
3 Sept 2026, 09:3329,443+38
2 Sept 2026, 04:1329,405+272
1 Sept 2026, 03:5329,133+167
31 Aug 2026, 00:1828,966+4
29 Aug 2026, 23:4428,962-11
28 Aug 2026, 20:2228,973+5
27 Aug 2026, 19:2428,968+9
26 Aug 2026, 22:4328,959+2
25 Aug 2026, 23:4728,957+3
24 Aug 2026, 21:3728,954-11
23 Aug 2026, 05:3628,965+26
21 Aug 2026, 19:3428,939+49
20 Aug 2026, 15:4728,890+123
19 Aug 2026, 13:4228,767+117
18 Aug 2026, 13:0428,650+810
17 Aug 2026, 13:3827,840+2,144
16 Aug 2026, 06:5625,696+203
15 Aug 2026, 02:3825,493first reading

Engagement

No public post preview. We read this entry on 15 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

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.

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.

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.

Navahang
@Navahang · 81,670
Telegram ranks this channel #72 of 73 here — alongside 72 others — read 19 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“Persian Cinema Club” (@PersianCinemaClub), 31,366 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/PersianCinemaClub.

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.