Channel
@nevsky_sindicate
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
110subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002809587287 |
|---|---|
| Type | Channel |
| Username | @nevsky_sindicate |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 8 September 2026 |
| On Telegram | t.me/nevsky_sindicate |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:26 | 110 | -1 |
| 9 Aug 2026, 06:48 | 111 | no change |
| 6 Aug 2026, 22:40 | 111 | first reading |
20 posts held, back to 20 February 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 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 20 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 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.
163 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 50.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 83 | 50.9% | |
| ❤ | 64 | 39.3% | |
| 👾 | 7 | 4.29% | |
| 🎉 | 4 | 2.45% | |
| 👏 | 3 | 1.84% | |
| 👍 | 1 | 0.613% | |
| 💘 | 1 | 0.613% |
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 19 of the 20 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 163 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 20 February 2026 to 27 July 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.
Продолжаем публиковать дурачковые видосики. Рассказываем как записывали певцов. В этот раз у нас было целых три ведущих голоса. Во первых, конечно же Адрюха. Во вторых, Милена, без которой уже сложно представить поход в студию. А еще в этот раз у нас отметилась специальная гостья. Тот кто досмотрит до конца узнает=)
🔥8
А вот про Мишу кстати рассказывает Денис, звукорежиссёр этого трека
Студия: Zaris. Барабанщик: Михаил Масленников. Ассистент записи: Богдан Панченко. С сессии записи барабанов для группы Невский Синдикат.
🔥4❤2
По сложившейся доброй традиции, видосики со студии. Барабаны и бас снимать одно удовольствие - только качественные дубли=)
🔥6❤1
Привет пупсики! Сегодня совершенно случайно заметил, что редакция Яндекс музыки взяла "Не всерьез" в свой редакторский плэйлист. Неожиданно приятная мелочь=)
🔥14❤3
трек на остальных стриммингах: https://zvonko.link/27529E1 приятного прослушивания!
❤3
трек на Яндекс музыке https://music.yandex.ru/album/42993750/track/153486134?utm_source=web&utm_medium=copy_link
❤8🔥2
Чмоки, пупсики! Меньше двух часов остается до главной премьеры этого лета. Самое время приготовить пунш и настроить свои радиоприемники!
🔥7👾4
Тыкайте на пресэйв, чтобы не проспать премьеру: https://band.link/0eAQz
❤2🔥2
Привет, пупсики! Рады видеть всех вас в самом разгаре лета! Конечно же, мы и сами не хотели оставаться в стороне от этой жаришки и кое-что для вас записали. Ловите наш летний блокбастер. 15 июля, ровно посередине лета, выходит наш трек "Не всерьез". В прошлый раз, мы с Андрюхой от души наигрались в ковбоев. Вообразим теперь, что ковбои выходят из бара, а на улице творятся интересные дела: ездят ретро-машины, танцуют…
❤7
что-то должно случиться... возможно, это будет новый релиз Невского Синдиката😄
🔥20👾3
И кстати, если уж речь про девушек, то как тут не вспомнить, что в подготовке нашего последнего релиза учавствовало целых четыре девчонки. Во первых, это наша незаменимая художница Юля, как всегда куча артов на все случаи жизни. Аж выбирать обложку пришлось всем коллективом. Пели с нами этот три московские девушки. Правда, до студии добралась в этот раз только Милена, с ней мы записываем уже второй трек. Но мы все ра…
❤4
Showing the 12 most recent of 20 posts we hold for @nevsky_sindicate. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 2 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
“Невский Синдикат” (@nevsky_sindicate), 110 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/nevsky_sindicate.
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.