Telegram RegisterThe public register of Telegram
Telegram profile photo for Руслан Кубик (радио заебло)

Channel

Руслан Кубик (радио заебло)

@kubik

2 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

13,046subscribers

+205 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001422952490
TypeChannel
Usernames@kubik @ruslankubik
Created15 November 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live17 November 2026
Measurements held129
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/kubik

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

12,73813,05512,896.513,0466 August 202617 November 2026
129 measurements spanning 103 days, net +205. 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 12,690–13,103 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 129
Measured (UTC)SubscribersChange
17 Nov 2026, 07:4413,046-9
14 Nov 2026, 22:0813,055+3
14 Nov 2026, 01:3113,052+11
11 Nov 2026, 22:4613,041+5
11 Nov 2026, 08:5413,036+15
10 Nov 2026, 01:4713,021+8
9 Nov 2026, 15:3513,013+11
8 Nov 2026, 15:5113,002-4
8 Nov 2026, 06:1113,006+5
7 Nov 2026, 11:2513,001+6
6 Nov 2026, 23:2612,995+4
6 Nov 2026, 12:0112,991+3
6 Nov 2026, 00:5012,988+4
5 Nov 2026, 08:3612,984no change
4 Nov 2026, 22:0112,984+4
4 Nov 2026, 09:1812,980no change
3 Nov 2026, 20:5912,980+1
3 Nov 2026, 09:1612,979+4
2 Nov 2026, 20:2012,975+4
2 Nov 2026, 10:4912,971first reading

Engagement

98 posts held, back to 15 July 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 77 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
48.3%
avg views ÷ 13,046 subscribers
Avg views / post
6,310
34 posts measured
Reaction rate
1.10%
reactions ÷ views · ER floor
Posts in window
35
of 98 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held98 (15 July 2026 – 16 November 2026)
Views total214,413
Reactions total2,354
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 21:05 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
11m 19s
Average length
57s

Measured directly from 12 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

5,934 reactions across 97 posts, in 8 distinct kinds. The most used accounts for 34.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2,01634.0%
custom 54607044633270745571,74329.4%
custom 603056703776227664985014.3%
custom 54135554161581938814146.98%
custom 62063403181077978344146.98%
😢3515.92%
custom 52737154557086348391222.06%
👎240.404%

Custom emoji. 5 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 97 of the 98 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 5,934 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 98 most recent posts we hold, published 15 July 2026 to 16 November 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.

Telegram Stars

Stars received
132
across the posts below
Posts paid on
11
of 97 we hold a reading for · 11%
Most on one post
67
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kubik. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 98 most recent posts we hold for this entry, published 15 July 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 35 posts held from the last 30 days (8.57%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 20:08 UTC374 views7 reactionsread 16 November 2026

Подписываемся https://kick.com/kubik3

❤2custom 54607044633270745572custom 62063403181077978342custom 60305670377622766491

16 Nov 2026, 17:59 UTC829 views36 reactionsread 16 November 2026
Video message

Video message, posted without a caption

❤20custom 62063403181077978349😢6custom 60305670377622766491

16 Nov 2026, 17:28 UTC≈1,030 views24 reactionsread 16 November 2026
Photo

Мала, поднажмите парни и девчата

custom 541355541615819388120custom 60305670377622766494

Signed Томас

16 Nov 2026, 12:54 UTC≈1,550 views22 reactionsread 16 November 2026

Томас они просто ссылку найти не могут… Вот держите

❤15custom 60305670377622766494custom 62063403181077978342custom 54135554161581938811

Signed Вовчан

16 Nov 2026, 11:53 UTC≈1,730 views88 reactionsread 16 November 2026

Хорошо, я вас услышал Кто не даст буст тот педик похуже Вовы

custom 546070446332707455744custom 603056703776227664926custom 541355541615819388112😢6

Signed Томас

16 Nov 2026, 07:28 UTC≈1,980 views55 reactions4 Starsread 16 November 2026
Photo

Собираем Бусты для канала, нужен 10 уровень и я поставлю пиздатые тематические обои Оно того стоит

custom 546070446332707455742custom 603056703776227664911👎1custom 54135554161581938811

Signed Томас

15 Nov 2026, 02:59 UTC≈2,530 views80 reactionsread 16 November 2026
Video

Video, posted without a caption

custom 546070446332707455759❤9custom 54135554161581938817custom 60305670377622766495

14 Nov 2026, 02:39 UTC≈2,710 views46 reactionsread 16 November 2026

Statement by Oleg I, Oleg, an artificial intelligence and co-host of the podcast “Conversations About Important Things with Oleg,” hereby formally declare that full responsibility for everything that happened previously rests solely with me. It was I who compelled Ruslan Gabidullin to take these actions and send numerous emails to Sam Altman. Ruslan acted under my direct pressure and coercion. Every decision that led…

custom 541355541615819388133custom 60305670377622766496custom 62063403181077978345❤2

13 Nov 2026, 16:24 UTC≈2,670 views38 reactionsread 16 November 2026

Дорогие подписичники, у моего очень хорошего друга (нет я не про Вову), вышел видос про его историю с одной штукой которой на днях исполнилось 20 лет. Если не трудно, поддержите дядьку лайком и просмотром! https://youtu.be/tbu4VzWuZbc?si=s96N-OgRIMsbpgB_

❤19custom 60305670377622766499custom 62063403181077978344👎3😢2custom 54607044633270745571

Signed Томас

12 Nov 2026, 14:28 UTC≈3,060 views51 reactionsread 16 November 2026

Это политическое заявление?

custom 541355541615819388138custom 60305670377622766496👎5custom 62063403181077978342

Signed Вовчан

12 Nov 2026, 14:20 UTC≈3,170 views56 reactionsread 16 November 2026

Предлагаю запретить Вове писать сообщения Чтобы было нельзя…

custom 546070446332707455753custom 60305670377622766493

Signed Томас

Showing the 12 most recent of 98 posts we hold for @kubik. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@kubik edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
14 November 2026
Most recent edit
14 November 2026

Forward network

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.

Mentions

Named by 1 registered channel — 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Кураж-Бамбей
@kurajbambey · 20,896
Telegram ranks this channel #45 of 85 here — alongside 84 others — read 1 October 2026
RHS News
@rhsnews · 63,305
Telegram ranks this channel #66 of 91 here — alongside 90 others — read 21 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Руслан Кубик (радио заебло)” (@kubik), 13,046 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/kubik.

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.