Telegram RegisterThe public register of Telegram

Bot

Скачать песню найти музыка из

@YandexPesniBot

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

48,215monthly users

+215 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 ID6332392299
TypeBot
Username@YandexPesniBot
First recorded12 August 2026
Last confirmed live14 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/YandexPesniBot

Growth

47,93748,21548,0767 August 2026 — 48,000 monthly users9 August 2026 — 48,065 monthly users11 August 2026 — 48,059 monthly users12 August 2026 — 47,937 monthly users12 August 2026 — 47,937 monthly users13 August 2026 — 48,007 monthly users14 August 2026 — 48,215 monthly users7 August 202614 August 2026
7 measurements spanning 7 days, net +215. 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 47,895–48,257 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
14 Aug 2026, 21:3748,215+208
13 Aug 2026, 13:0848,007+70
12 Aug 2026, 16:5447,937no change
12 Aug 2026, 10:4747,937-122
11 Aug 2026, 12:0348,059-6
9 Aug 2026, 15:1548,065+65
7 Aug 2026, 18:4748,000first 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 23 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.

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.

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

“Скачать песню найти музыка из” (@YandexPesniBot), 48,215 monthly users as measured 14 August 2026. Telegram Register, tgregister.com/channel/YandexPesniBot.

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.