Telegram RegisterThe public register of Telegram
Telegram profile photo for nazarova

Channel

nazarova

@playnazarova

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

157subscribers

+8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002337486176
TypeChannel
Username@playnazarova
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/playnazarova

Growth

149158153.57 August 2026 — 149 subscribers8 August 2026 — 149 subscribers16 August 2026 — 153 subscribers23 August 2026 — 158 subscribers29 August 2026 — 156 subscribers7 September 2026 — 157 subscribers1577 August 20267 September 2026
6 measurements spanning 31 days, net +8. 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 148–159 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 07:01157+1
29 Aug 2026, 20:02156-2
23 Aug 2026, 13:56158+5
16 Aug 2026, 05:18153+4
8 Aug 2026, 20:15149no change
7 Aug 2026, 16:02149first reading

Engagement

13 posts held, back to 17 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 08s
Average length
32s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

81 reactions across 12 posts, in 15 distinct kinds. The most used accounts for 22.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1822.2%
💘1721.0%
custom 520892613604148396689.88%
custom 534165707950759509967.41%
custom 535731550377163488967.41%
custom 535717104254663068744.94%
custom 544759109065377055644.94%
🕊44.94%
😭44.94%
🥰33.70%
💔22.47%
💯22.47%
custom 542497283509532974211.23%
🍓11.23%
😱11.23%

Custom emoji. 6 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 12 of the 13 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 81 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 17 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 17:03 UTC39 views5 reactionsread 8 August 2026
Photo

Вот тут можно сделать репост , написать комментарий , ну короче вы знаете что делать🧿 Мяу

🔥4🕊1

7 Aug 2026, 16:56 UTC33 views8 reactionsread 8 August 2026
Video message

Video message, posted without a caption

💘4😭2custom 52089261360414839662

7 Aug 2026, 16:42 UTC51 views8 reactionsread 8 August 2026
Video

mua в сети , ребятаааа💋💔 Слушать 👈🏻 music prod: garleem manager:

custom 53416570795075950993💔1🔥1😱1custom 53571710425466306871custom 53573155037716348891

3 Aug 2026, 15:36 UTC75 views7 reactionsread 8 August 2026
Video

Ребята , трек mua скорооо Пресейв делаем тут

🔥4😭1custom 53571710425466306871custom 53573155037716348891

3 Aug 2026, 14:00 UTC65 views6 reactionsread 8 August 2026
Video message

Video message, posted without a caption

💘4🥰1custom 54475910906537705561

29 Jul 2026, 18:46 UTC116 views4 reactionsread 8 August 2026

Я надеюсь, вы влюблены/любите по-настоящему, чтобы целоваться с любимыми 💋

💘1😭1custom 52089261360414839661custom 53573155037716348891

29 Jul 2026, 18:45 UTC111 views12 reactionsread 8 August 2026
Photo

Уже куча всего произошло, а я тут ничего не рассказываю, оцениваем мои навыки ведения ТГК …😂 1. Я подписалась с лейблом 🥹новый трек выпускаю с ребятами HEDLINER music 2. Скоро выход трека mua💋 позже будет ссылка на пресейв 3. Режим вышел из чата , пытаюсь наладить , но пока не получаеццца, потому что лечу на бешенных скоростях 🚀

🔥5🥰2custom 53416570795075950992custom 53571710425466306871custom 53573155037716348891custom 54249728350953297421

26 Jul 2026, 17:44 UTC106 views3 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🍓1💘1🕊1

23 Jul 2026, 16:45 UTC127 views3 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 52089261360414839661custom 53416570795075950991custom 53573155037716348891

23 Jul 2026, 16:14 UTC127 views5 reactionsread 8 August 2026
Photo

сегодня снимаем промо для моего нового трека muaaa говорю себе : «Дашуля, ты всё успеваешь» вроде, помогает

custom 54475910906537705563💔1custom 52089261360414839661

20 Jul 2026, 21:48 UTC149 views11 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥4💘2💯2custom 52089261360414839661custom 53571710425466306871custom 53573155037716348891

Showing the 12 most recent of 13 posts we hold for @playnazarova. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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

“nazarova” (@playnazarova), 157 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/playnazarova.

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.