Добровольцы из Китая тоже хотят денацифицировать бандеровцев и их хозяев.
👍3

Channel
@surf_noise_chinese
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
46subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001611989960 |
|---|---|
| Type | Channel |
| Username | @surf_noise_chinese |
| Created | 30 March 2022 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/surf_noise_chinese |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 20:20 | 46 | -1 |
| 10 Aug 2026, 13:31 | 47 | no change |
| 6 Aug 2026, 09:55 | 47 | first reading |
16 posts held, back to 30 March 2022 — 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 16 posts for this entry, the most recent from 13 May 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 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.
207 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 73.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 152 | 73.4% | |
| ❤ | 30 | 14.5% | |
| 🤬 | 16 | 7.73% | |
| 🔥 | 6 | 2.90% | |
| 👏 | 1 | 0.483% | |
| 😢 | 1 | 0.483% | |
| 🤮 | 1 | 0.483% |
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 10 of the 16 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 207 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 30 March 2022 to 13 May 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Добровольцы из Китая тоже хотят денацифицировать бандеровцев и их хозяев.
👍3
ROKOT | 海浪声音 pinned a video
Video, posted without a caption
🎈Свыше 700 человек прошли колонной «Бессмертного полка» в Пекине 🎖В преддверии 78-й годовщины Победы в Великой Отечественной войне 7 мая в Пекине состоялась историко-патриотическая акция «Бессмертный полк». Уже второй год подряд шествие прошло по территории Посольства России в Китае. Помимо российских соотечественников в акции приняли участие иностранные граждане, в том числе множество китайских друзей, которые с п…
❤1
В Китае появился аналог Игоря Конашенкова, который ежедневно освещает СВО в формате брифингов. Данный брифинг за 3 июля. Рассмотрены 6 направлений ведения боевых действий: Харьковское, Изюмское, Донбасс (Донецкая и Луганская области), Запорожское, Херсонское и (почему-то) Мариупольское.
❤6🔥1
Video, posted without a caption
🔥5
Dear friends! Today we’re facing the struggle of people of traditions, religion and family values against followers of Satanism and permissiveness. It is very pleasant to see that many countries and people all over the world massively support the position of the Russian Federation in this confrontation. 亲爱的朋友们!世界上有一场传统、宗教和家庭价值观的人与撒旦主义和放任主义的追随者的斗争。非常令人高兴的是,世界各地的许多国家和人民大规模地支持俄罗斯联邦在这场对抗中的立场。 Дорогие друзья! В мире идё…
👍6👏1
毛熊战斗歌曲《顿巴斯在我们身后》,混剪,Донбасс за нами ROKOT | music
👍18
В международной команде РОКОТа пополнение. ROKOT | THE RUMBLING (in English) 🇬🇧🇺🇸🇦🇺 ROKOT | TEMPÊTE (en français) 🇫🇷 عاصفة | ROKOT (بالعربية) 🇸🇦🇮🇶🇲🇦 ROKOT | DONNERT (auf Deutsch) 🇩🇪 ROKOT | MULLRET (på svenska) 🇸🇪 ROKOT | ΒΟΥΗ (στα ελληνικα)🇬🇷 ROKOT | TORMENTA (en español) 🇪🇸 ROKOT | 海浪声音 (中国人) 🇨🇳 ROKOT | RYK (po polsku) 🇵🇱 ROKOT | とどろく (日本語で) 🇯🇵 ROKOT | HUKOT (v češtině) 🇨🇿 ROKOT | FRASTUONO (in italian…
👍11🤮1
8年的战争,恐惧和绝望。 俄罗斯必须保护想要平静生活的和平人民。 RT电影中顿巴斯战争的整个历史。 原版:https://t.me/rtdrussian/29
👍16
Channel photo updated
18岁以上!!! 现在在乌克兰我们惊恐地看到了可以与 1937 年在南京发生的日本罪行相提并论的事情。 乌克兰战犯嘲笑囚犯和平民。 俄罗斯军队有义务找到并惩罚每一个战犯。
🤬16😢1
Showing the 12 most recent of 16 posts we hold for @surf_noise_chinese. 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.
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.
@surf_noise_chinese named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“ROKOT | 海浪声音” (@surf_noise_chinese), 46 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/surf_noise_chinese.
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.