Telegram RegisterThe public register of Telegram
Telegram profile photo for RegaSpotify | ربات دانلود اسپاتیفای

Bot

RegaSpotify | ربات دانلود اسپاتیفای

@RegaSpotify_Bot

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

134,406monthly users

-12,361 since we began measuring on 5 August 2026

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

Register entry

Telegram ID5360488345
TypeBot
Username@RegaSpotify_Bot
First recorded6 August 2026
Last confirmed live26 August 2026
Measurements held18
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/RegaSpotify_Bot

Topic

Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 40% 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.

Growth

134,406147,188140,7975 August 2026 — 146,767 monthly users6 August 2026 — 146,767 monthly users7 August 2026 — 147,107 monthly users7 August 2026 — 146,905 monthly users9 August 2026 — 147,188 monthly users11 August 2026 — 146,995 monthly users11 August 2026 — 146,778 monthly users12 August 2026 — 146,448 monthly users14 August 2026 — 146,417 monthly users15 August 2026 — 146,956 monthly users17 August 2026 — 146,896 monthly users19 August 2026 — 146,818 monthly users20 August 2026 — 146,588 monthly users21 August 2026 — 146,568 monthly users22 August 2026 — 146,847 monthly users24 August 2026 — 146,692 monthly users25 August 2026 — 137,168 monthly users26 August 2026 — 134,406 monthly users5 August 202626 August 2026
18 measurements spanning 20 days, net -12,361. 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 132,489–149,105 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
26 Aug 2026, 09:17134,406-2,762
25 Aug 2026, 09:55137,168-9,524
24 Aug 2026, 09:28146,692-155
22 Aug 2026, 18:16146,847+279
21 Aug 2026, 08:26146,568-20
20 Aug 2026, 05:53146,588-230
19 Aug 2026, 07:38146,818-78
17 Aug 2026, 10:38146,896-60
15 Aug 2026, 16:58146,956+539
14 Aug 2026, 03:17146,417-31
12 Aug 2026, 23:54146,448-330
11 Aug 2026, 23:24146,778-217
11 Aug 2026, 02:02146,995-193
9 Aug 2026, 23:36147,188+283
7 Aug 2026, 23:35146,905-202
7 Aug 2026, 03:08147,107+340
6 Aug 2026, 18:25146,767no change
5 Aug 2026, 23:00146,767first 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.

Forward network

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

“RegaSpotify | ربات دانلود اسپاتیفای” (@RegaSpotify_Bot), 134,406 monthly users as measured 26 August 2026. Telegram Register, tgregister.com/channel/RegaSpotify_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.