Telegram RegisterThe public register of Telegram
Telegram profile photo for Кубок Пороля

Channel

Кубок Пороля

@porol_cup

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

76subscribers

-2 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003950637837
TypeChannel
Username@porol_cup
CreatedBetween 1 April 2026 and 25 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live19 September 2026
Measurements held5
Confirmed unchanged4 times, most recently 19 September 2026
On Telegramt.me/porol_cup

Growth

767977.58 August 2026 — 78 subscribers8 August 2026 — 79 subscribers9 August 2026 — 79 subscribers16 August 2026 — 77 subscribers23 August 2026 — 76 subscribers8 August 202623 August 2026
5 measurements spanning 15 days, net -2. 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 76–79 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 11:4976-1
16 Aug 2026, 07:2677-2
9 Aug 2026, 19:3179no change
8 Aug 2026, 20:1879+1
8 Aug 2026, 06:0178first reading

Engagement

20 posts held, back to 25 June 2026the 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

117 reactions across 14 posts, in 16 distinct kinds. The most used accounts for 24.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2924.8%
🤔2319.7%
2218.8%
😭75.98%
🤡75.98%
❤‍🔥43.42%
🙏43.42%
🎃32.56%
🏆32.56%
👎32.56%
😁32.56%
💅21.71%
💔21.71%
😨21.71%
🙉21.71%
😢10.855%

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 15 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 117 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 25 June 2026 to 7 August 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

7 Aug 2026, 17:51 UTC76 views4 reactionsread 9 August 2026

Будем рады вашим отзывам на турнир здесь и в обсуждении пакета Если вдруг захотите его приобрести для локальных отыгрышей и тренировок, то пишите по указанным в описании контактам Через пару недель возможно будет анонс нового турнира в новом формате

😨2❤‍🔥1🤡1

7 Aug 2026, 17:50 UTC116 views19 reactionsread 9 August 2026

Финал завершён! 🥇Константин Мишкин 180 🥈Киберт Артём 100 🥉Костенко Серафима 30 4 Биктимиров Тимур 10 Поздравляем всех призёров и победителей!

🔥133❤‍🔥3

7 Aug 2026, 16:57 UTC88 viewsread 9 August 2026

Финал скоро начнётся, желающие могут подключиться для прослушивания https://telemost.yandex.ru/j/42016481326492

6 Aug 2026, 18:05 UTC89 views7 reactionsread 9 August 2026

Завтра состоится финал нашего турнира! Желающие смогут подключиться к трансляции в 20:00 по мск

🔥6🤡1

24 Jul 2026, 09:41 UTC199 views8 reactionsread 9 August 2026

Друзья! Состав финалистов полностью определён, к ним присоединились Биктимиров Тимур и Мишкин Константин! Поздравляем! Финал будет сыгран скорее всего на следующей неделе. Ждём с нетерпением

5💔2🔥1

23 Jul 2026, 14:24 UTCviews —26 reactionsread 9 August 2026

Posted without readable text

🤔16😭4😁3💅2👎1

20 Jul 2026, 20:26 UTC219 views5 reactionsread 9 August 2026

Пятый этап сыгран, остался последний бой перед финалом Пакет будет выложен завтра

5

16 Jul 2026, 13:46 UTC258 views13 reactionsread 9 August 2026

Четвёртый этап завершился и мы готовы представить первых двух финалистов: Серафима Костенко и Артём Киберт! Чаты пятого этапа соберём сегодня-завтра, пакет выложим так же. Всем удачи в пятом этапе

🔥8😭3👎2

14 Jul 2026, 12:26 UTC243 views8 reactionsread 9 August 2026

Друзья, сегодня последний день, когда мы напоминаем вам выбрать время для боя. Если вы этого не сделаете, то мы выберем время сами и проведём для тех, кто в это время сможет играть. Спасибо за внимание

🤡5🙉2😢1

13 Jul 2026, 09:29 UTC242 viewsread 9 August 2026

Третий этап доигран, чаты четвёртого собраны. Уже в этом этапе мы узнаем двух первых финалистов! Пакет 3 этапа будет выложен в обсуждение сегодня

7 Jul 2026, 19:24 UTC289 views7 reactionsread 9 August 2026

Пакет второго этапа выложен в обсуждение

🙏4🎃3

6 Jul 2026, 18:12 UTC282 views6 reactionsread 9 August 2026
Photo

Доигран и второй этап Чаты третьего будут скоро собраны, а темы второго будут выложены в канал обсуждения upd: чаты собраны 👍👍

6

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

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.

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

“Кубок Пороля” (@porol_cup), 76 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/porol_cup.

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.