Telegram RegisterThe public register of Telegram
Telegram profile photo for Homayounorg | همایون

Channel

Homayounorg | همایون

@Homayounorg

Has discussion group

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

5,400subscribers

-84 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001169219591
TypeChannel
Username@Homayounorg
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live5 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/Homayounorg

Growth

5,4005,4845,4427 August 2026 — 5,484 subscribers7 August 2026 — 5,483 subscribers10 August 2026 — 5,476 subscribers13 August 2026 — 5,468 subscribers17 August 2026 — 5,462 subscribers20 August 2026 — 5,456 subscribers24 August 2026 — 5,440 subscribers26 August 2026 — 5,431 subscribers29 August 2026 — 5,421 subscribers31 August 2026 — 5,421 subscribers1 September 2026 — 5,406 subscribers5 September 2026 — 5,400 subscribers7 August 20265 September 2026
12 measurements spanning 29 days, net -84. 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 5,387–5,497 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 01:385,400-6
1 Sept 2026, 17:045,406-15
31 Aug 2026, 12:015,421no change
29 Aug 2026, 11:565,421-10
26 Aug 2026, 19:245,431-9
24 Aug 2026, 01:565,440-16
20 Aug 2026, 00:285,456-6
17 Aug 2026, 11:085,462-6
13 Aug 2026, 11:265,468-8
10 Aug 2026, 04:475,476-7
7 Aug 2026, 12:275,483-1
7 Aug 2026, 04:215,484first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.

نایاب رپی | Nayab Rapi
@nayabrapi · 30,829
Telegram ranks this channel #51 of 82 here — alongside 81 others — read 6 September 2026
پرامپت | هوش مصنوعی
@promptfre · 441,107
Telegram ranks this channel #53 of 74 here — alongside 73 others — read 10 August 2026
Rapfarsi
@rapfarsipsw · 103,520
Telegram ranks this channel #74 of 75 here — alongside 74 others — read 15 August 2026
mhtimusic
@blacknotemusic · 6
Telegram ranks this channel #76 of 82 here — alongside 81 others — read 15 August 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“Homayounorg | همایون” (@Homayounorg), 5,400 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/Homayounorg.

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.