Channel
@poluryba
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Declared links · Cite this entry
67subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002219040341 |
|---|---|
| Type | Channel |
| Username | @poluryba |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/poluryba |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 19:57 | 67 | -1 |
| 10 Aug 2026, 01:01 | 68 | no change |
| 8 Aug 2026, 04:15 | 68 | first reading |
8 posts held, back to 21 December 2025 — 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 8 posts for this entry, the most recent from 7 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
52 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 40.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 21 | 40.4% | |
| 👍 | 20 | 38.5% | |
| ❤🔥 | 3 | 5.77% | |
| 🏆 | 3 | 5.77% | |
| 🍾 | 2 | 3.85% | |
| 🌭 | 1 | 1.92% | |
| 🐳 | 1 | 1.92% | |
| 😱 | 1 | 1.92% |
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 8 of the 8 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 52 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 21 December 2025 to 7 May 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.
Завтра отправляюсь с командой Хариусы в Карелию на реку Укса. Вся группа будет сплавляться на Варгах и это будет мой первый опыт сплава по порогам на пакрафте. Давно об этом мечтал. Во вторник делал тестовую загрузка Варга. Все поместилось но с гермой на корме. Сейчас прикидываю и думаю,что скорее всего на месте получится всё уложить внутрь. Это я смогу проверить только в субботу,когда мы доберёмся до речки, а пока э…
👍3🔥3😱1
За участие в "Скитульском забегалове", компания Вольный ветер подарили сертификат на 5000 р. Сегодня съездил к ним в магазин и стал счастливым обладателем нового надувного спас жилета. Тестировать буду в Карелии! Ещё раз спасибо Инне Порошиной за подарки!
👍5🔥3🌭1
Спасибо Олегу Губарёву за то,что продал мне чемпионский пакрафт, составил честную конкуренцию и подбил меня участвовать на "Скитульском забегалове". Спасибо Инне Порошиной и компании Вольный Ветер, что приняли меня в свою команду на "Скитульское забегалово". Спасибо компании КаякВПрокат.РФ , за то,что посоветовали меня,как отличного пакрафтера для "Скитульского Забегалова" Спасибо моей семье,за то что любят меня …
🔥6
Это свершилось!🥈 4 года я шёл до этого момента,чтобы в честной борьбе занять призовое место на Скитульце. Проиграл только мастеру спорта и это даже почётно. Безумно рад и счастлив,что добился этого! Спасибо организаторам фестиваля «СКИТУЛЕЦ» за такую возможность! Спасибо моей банде Полурыба ,что верили в меня!🧜 Спасибо КОМАНД ХАРИУСЫ, что разделили со мной #XXскитулец !
👍3🔥1
Команда "Полурыба" поздравляет всех с Новым годом! Пусть каждый из вас найдёт своё русло и самореализуется! Успехов и удачи в Новом году!🎄
🔥6❤🔥3
Эдит про сплав на фестивале "Пломбир"
👍5🍾2
🎁А ещё каким то чудом выиграл вчера сертификат на бесплатное участие в одном из этапов Тверского гребного марафона.🚣 🥳Безумно рад такому подарку. 💪Планирую в следующем году пройти все этапы. Присоединяйтесь, будем вместе участвовать!
🏆3👍2
Вчера посетили великолепный фестиваль "Пломбир" от команды FreeSup. Доброжелательная атмосфера, теплая погода, прекрасные люди. На финише вкусная еда, баня и подарки. Вчера впервые узнал и попробовал блюдо "Басма"(это крупно нарезанные тушёные овощи с мясом). Презентация блюда была на высшем уровне. Спасибо организаторам и участникам мероприятия. Было классно!
👍2🔥2🐳1
Showing the 8 most recent of 8 posts we hold for @poluryba. 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.
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.
2 URLs this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“ПОЛУРЫБА” (@poluryba), 67 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/poluryba.
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.