Что-то я тут резко понял, что даже и не показывал вам ее, не хвастался 😁
❤16🔥6🥰2

Channel
@novikovfriendly
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
790subscribers
-15 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002277603652 |
|---|---|
| Type | Channel |
| Username | @novikovfriendly |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/novikovfriendly |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 09:37 | 790 | -7 |
| 22 Aug 2026, 19:52 | 797 | -7 |
| 14 Aug 2026, 14:17 | 804 | -1 |
| 8 Aug 2026, 01:34 | 805 | no change |
| 7 Aug 2026, 14:06 | 805 | first reading |
17 posts held, back to 16 March 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 17 posts for this entry, the most recent from 13 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
226 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 46.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 104 | 46.0% | |
| 🔥 | 40 | 17.7% | |
| 😁 | 20 | 8.85% | |
| 😢 | 19 | 8.41% | |
| 🫡 | 15 | 6.64% | |
| custom 5402099007507934020 | 13 | 5.75% | |
| 🤔 | 10 | 4.42% | |
| 🥰 | 5 | 2.21% |
Custom emoji. One row above is a 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 count beside it isTelegram’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 17 of the 17 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 226reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 16 March 2026 to 13 June 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.
Что-то я тут резко понял, что даже и не показывал вам ее, не хвастался 😁
❤16🔥6🥰2
Поздравляю нас с 3 местом во 2 дивизионе ⚡️ Удачи нам на продвижении 🍀
❤9🔥1
Быстрый матч был, я только одного не понял, почему они двумя бешками не ехали гору перезабирать сразу? Очевидно же что мы будем ст откидывать и разрядимся, они проехали бы и встали базиками на откид нашего заката, хуйня какая-то короче
🤔10
Да в пизду ваш киберспорт
😁10🔥2❤1
Ебать я плохо матч отыграл, чмо я А вообще обидно, снова все катки сами отдали 🫡
🫡8❤1
Что там как во 2 диве? Прервали эту серию побед непобедимых, но могли лучше сыграть, как всегда впрочем
❤5🥰3
Нормальный матч? Как впечатления ваще
❤11🔥1custom 54020990075079340201
Теорию в ГАИ сдал, матч выиграл, что еще нужно для счастья
❤9🔥5
Ошибались они меньше чем мы, а мы мусор, поэтому проебали, ну типа… Каждый раз одно и тоже я хуй знает
😢7❤4🔥1
Стрим сегодня в 20:00, я вместе со shtyr3 будем разбирать прошедшие матчи команды VIOLENCE и делать предикты на 2 и 1 дивизионы!
😁8❤5🔥2
Мусорята мы конкретные, но этот момент красивый 🔫
❤10🔥3
Как вам матч?
🔥7❤4
Showing the 12 most recent of 17 posts we hold for @novikovfriendly. 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Novikov” (@novikovfriendly), 790 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/novikovfriendly.
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.