Telegram RegisterThe public register of Telegram

Channel

🩵Окунь🩵

@okynbbrawl

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

502subscribers

+0 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-1002336243270
TypeChannel
Username@okynbbrawl
Description🔔ʙ ϶ᴛоʍ ᴋᴀнᴀᴧᴇ ʙы ʍожиᴛᴇ уʙидᴇᴛь ʍноᴦо ᴀᴩᴛоʙ, конкурсов на звезды, и много чего еще 🔹владелец - @okynek_xd 🔹прайс на рекламу и покупку товаров в bs - https://t.me/prays_okynek 🔹отзывы - https://t.me/otzyvy_okynek 🔹чат - https://t.me/brawlstarsokynb
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 live8 August 2026
Measurements held2
On Telegramt.me/okynbbrawl

Growth

5027 Aug 2026, 16:15 — 502 subscribers8 Aug 2026, 04:17 — 502 subscribers7 Aug 2026, 16:158 Aug 2026, 04:17
2 measurements taken within a single day. 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 501–503 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 04:17502no change
7 Aug 2026, 16:15502first reading

Engagement

20 posts held, back to 12 August 2025the 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 20 posts for this entry, the most recent from 5 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
501
Videos
13
Links
171

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

226 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 46.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤩10646.9%
❤‍🔥6026.5%
🤔2310.2%
🤪146.19%
🫡104.42%
😭83.54%
custom 541109722598606390041.77%
🗿10.442%

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 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 226reactions 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 12 August 2025 to 5 February 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

5 Feb 2026, 17:38 UTC168 views6 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

🤪5🤔1

Signed 𝗢𝗸𝘆𝗻𝗲𝗸 | звезды 1,5

31 Dec 2025, 11:37 UTC296 views22 reactionsread 8 August 2026

Привет

🤔12🤩5custom 54110972259860639004😭1

Signed 𝗢𝗸𝘆𝗻𝗲𝗸

21 Aug 2025, 11:30 UTC580 views5 reactionsread 8 August 2026
Photo

Конкурс на 🧸 х2 1-2 место : 🧸 Условия быть подписанным на : @re5le @alekzzgg1 Итоги на 80 кликов

❤‍🔥4😭1

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

20 Aug 2025, 17:12 UTC534 views10 reactionsread 8 August 2026
Photo

Конкурс на 🧸 х2 1-2 место : 🧸 Условия быть подписанным на : @dankussNews @APOOnews Итоги на 80 кликов

❤‍🔥8🤩2

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

19 Aug 2025, 17:24 UTC424 views9 reactionsread 8 August 2026
Photo

Конкурс на 🧸 х2 1-2 место : 🧸 Условия быть подписанным на : @Karasbbrawl @newsoriginal2 Итоги на 80 кликов

🤔9

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

18 Aug 2025, 15:11 UTC310 views35 reactionsread 8 August 2026

📢Проверка актива,рыбки! 5🤩- хуже некуда 10🤩-плохо 20🤩-пойдет,можно лучше 30🤩-норм 40🤩-отлично 50🤩-молодцы рыбки,Имба!

🤩34😭1

Signed Окунь ( 140 + отзывов ) #OKYN #dcn #Fox3 #ARS

18 Aug 2025, 10:45 UTC≈1,120 views10 reactionsread 8 August 2026
Photo

Конкурс на 🧸 х2 1-2 место : 🧸 Условия быть подписанным на : @nftsliva @rainbs666 Итоги на 80 кликов

❤‍🔥8🤪2

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

17 Aug 2025, 17:06 UTC546 views7 reactionsread 8 August 2026
Photo

Конкурс на 🧸 х2 1-2 место : 🧸 Условия быть подписанным на : @PEPEGIFTCH @maxproBB Итоги на 60 кликов

❤‍🔥4🤩3

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

17 Aug 2025, 10:19 UTC268 views19 reactionsread 8 August 2026
Photo

Запечатлел посхалку 1488 Как вам? 🤩-имбооо)

🤩19

Signed Окунь ( 140 + отзывов ) #OKYN #dcn #Fox3 #ARS

17 Aug 2025, 09:31 UTC702 views7 reactionsread 8 August 2026
Photo

Конкурс на 🧸 х3 1-3 место : 🧸 Условия быть подписанным на : @KRESTNAMEFEE @sonvey228 Итоги на 80 кликов

❤‍🔥6🤔1

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

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

Mentions

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.

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

“🩵Окунь🩵” (@okynbbrawl), 502 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/okynbbrawl.

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.