Telegram RegisterThe public register of Telegram
Telegram profile photo for 优影臻享

Bot

优影臻享

@Youxiu_bot

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

66,578monthly users

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

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

Register entry

Telegram ID7487350635
TypeBot
Username@Youxiu_bot
First recorded11 August 2026
Last confirmed live6 September 2026
Measurements held17
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/Youxiu_bot

Growth

64,65268,40866,5307 August 2026 — 64,652 monthly users10 August 2026 — 66,470 monthly users11 August 2026 — 66,767 monthly users11 August 2026 — 66,767 monthly users12 August 2026 — 66,326 monthly users15 August 2026 — 65,658 monthly users18 August 2026 — 67,887 monthly users19 August 2026 — 67,917 monthly users20 August 2026 — 67,985 monthly users21 August 2026 — 67,680 monthly users24 August 2026 — 66,641 monthly users25 August 2026 — 68,408 monthly users27 August 2026 — 68,215 monthly users30 August 2026 — 68,055 monthly users1 September 2026 — 67,698 monthly users4 September 2026 — 67,004 monthly users6 September 2026 — 66,578 monthly users66,5787 August 20266 September 2026
17 measurements spanning 30 days, net +1,926. 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 64,089–68,971 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
6 Sept 2026, 12:4066,578-426
4 Sept 2026, 00:5967,004-694
1 Sept 2026, 15:5267,698-357
30 Aug 2026, 13:3468,055-160
27 Aug 2026, 18:4768,215-193
25 Aug 2026, 19:0468,408+1,767
24 Aug 2026, 19:5366,641-1,039
21 Aug 2026, 14:0667,680-305
20 Aug 2026, 11:0367,985+68
19 Aug 2026, 10:5967,917+30
18 Aug 2026, 11:2667,887+2,229
15 Aug 2026, 20:5165,658-668
12 Aug 2026, 07:3366,326-441
11 Aug 2026, 16:3866,767no change
11 Aug 2026, 09:3266,767+297
10 Aug 2026, 06:4566,470+1,818
7 Aug 2026, 12:2464,652first 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 7 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“优影臻享” (@Youxiu_bot), 66,578 monthly users as measured 6 September 2026. Telegram Register, tgregister.com/channel/Youxiu_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.