Telegram RegisterThe public register of Telegram
Telegram profile photo for سوپر ایرانی وطنی آمریکایی

Bot

سوپر ایرانی وطنی آمریکایی

@Ciudgoy_bot

On this record: Growth · Engagement · Citations · Cite this entry

18,657monthly users

+1,257 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8600087124
TypeBot
Username@Ciudgoy_bot
First recorded16 August 2026
Last confirmed live29 August 2026
Measurements held15
Confirmed unchanged2 times, most recently 29 August 2026
On Telegramt.me/Ciudgoy_bot

Growth

17,40020,79419,0977 August 2026 — 17,400 monthly users9 August 2026 — 18,629 monthly users11 August 2026 — 19,238 monthly users12 August 2026 — 20,391 monthly users14 August 2026 — 20,622 monthly users15 August 2026 — 20,547 monthly users16 August 2026 — 20,547 monthly users18 August 2026 — 20,375 monthly users19 August 2026 — 20,553 monthly users20 August 2026 — 20,741 monthly users21 August 2026 — 20,794 monthly users23 August 2026 — 19,831 monthly users25 August 2026 — 19,336 monthly users27 August 2026 — 19,283 monthly users28 August 2026 — 18,657 monthly users18,6577 August 202628 August 2026
15 measurements spanning 21 days, net +1,257. 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 16,891–21,303 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
28 Aug 2026, 19:3818,657-626
27 Aug 2026, 22:1719,283-53
25 Aug 2026, 21:4319,336-495
23 Aug 2026, 12:3819,831-963
21 Aug 2026, 23:3720,794+53
20 Aug 2026, 18:2820,741+188
19 Aug 2026, 18:0620,553+178
18 Aug 2026, 18:0520,375-172
16 Aug 2026, 17:2420,547no change
15 Aug 2026, 16:0820,547-75
14 Aug 2026, 01:0820,622+231
12 Aug 2026, 21:1320,391+1,153
11 Aug 2026, 17:4819,238+609
9 Aug 2026, 16:0418,629+1,229
7 Aug 2026, 13:0217,400first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 3 registered channels — 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.

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

“سوپر ایرانی وطنی آمریکایی” (@Ciudgoy_bot), 18,657 monthly users as measured 28 August 2026. Telegram Register, tgregister.com/channel/Ciudgoy_bot.

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.