Telegram RegisterThe public register of Telegram
Telegram profile photo for Packrafters.Adventure|Пакрафт-прокат

Channel

Packrafters.Adventure|Пакрафт-прокат

@Packrafters_Adventure

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

350subscribers

+8 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002187262153
TypeChannel
Username@Packrafters_Adventure
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/Packrafters_Adventure

Topic

Other / unclassifiable — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 why it has no browse page of its own yet.

Growth

3423523476 August 2026 — 342 subscribers6 August 2026 — 342 subscribers14 August 2026 — 345 subscribers21 August 2026 — 347 subscribers29 August 2026 — 352 subscribers14 September 2026 — 350 subscribers3506 August 202614 September 2026
6 measurements spanning 38 days, net +8. 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 341–354 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 07:59350-2
29 Aug 2026, 08:16352+5
21 Aug 2026, 15:16347+2
14 Aug 2026, 18:23345+3
6 Aug 2026, 22:20342no change
6 Aug 2026, 22:00342first reading

Engagement

8 posts held, back to 13 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 8 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

47 reactions across 5 posts, in 10 distinct kinds. The most used accounts for 48.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2348.9%
👍1021.3%
36.38%
❤‍🔥36.38%
👏24.26%
🙏24.26%
12.13%
🎉12.13%
😁12.13%
🤩12.13%

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 5 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 47 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 13 June 2026 to 30 July 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

21 Jul 2026, 20:48 UTC204 views1 reactionsread 6 August 2026

На прошлых выходных провели очередной курс "Безопасность на бурной воде". На мероприятии присутствовал корреспондент из канала Water Accidents, так что с подробностями можно ознакомиться из независимого источника (см. репост ниже). А следующее наше мероприятие состоится 15-16 августа в слаломном канале Богородское и будет посвящено технике сплава на бурной воде. Запись в лс у Дениса Узикова @Johnny_go

1

21 Jul 2026, 20:48 UTC237 views18 reactionsread 6 August 2026
Forwarded from @water_accidentsPhoto

✅ 18-19.07.2026. Курс по безопасности на бурной воде, слаломный канал, село Богородское, Московская область. Никто не пострадал 😊 🇷🇺 Редкое для нашей страны мероприятие состоялось при полном аншлаге. Мы принимали участие в обучении и, признаться, были очень рады видеть столько мотивированных участников. Для всех, кто приехал на канал, осознанно важен системный подход к обеспечению безопасности своих увлечений. Благод

🔥9👍3👏21🎉1😁1🙏1

10 Jul 2026, 11:55 UTC631 views10 reactionsread 6 August 2026
Photo

Безопасность на бурной воде. Полный курс. 18–19 июля. Слаломный канал, Богородское. Друзья, продолжаем сезон тренировок! Следующий выезд посвящен фундаменту, без которого не обходится ни один серьезный сплав. 🆘 Зачем это нужно? Эти навыки — база для вашей личной и командной безопасности на любых сплавах, особенно в сложных условиях горных рек и настоящей бурной воды. Даже если вам кажется, что вы уже всё умеете и п

🔥5👍31🙏1

24 Jun 2026, 12:02 UTC355 views10 reactionsread 6 August 2026
Photo

На прошлых выходных провели очередную тренировку в слаломном канале Богородское — «Техника сплава по бурной воде». Погода порадовала, вода была отличная, и у многих участников уже заметен прогресс. А часть пакрафтеров даже пересела на каяки — и, похоже, получает от нового снаряда ещё больше эмоций и впечатлений 🚣‍♂️ Следующее мероприятие в Богородском состоится 18–19 июля. На этот раз тема — «Безопасность на бурной

🔥5❤‍🔥3👍1🤩1

16 Jun 2026, 11:16 UTC≈1,860 views8 reactionsread 6 August 2026
Photo

Уже в эти выходные (20-21 июня) состоится наш выезд в слаломный канал Богородское. Будем работать над техникой сплава по бурной воде на пакрафтах и каяках. Есть несколько свободных мест. Если вы думали присоединиться, то сейчас самое время написать @Oleg_Minaev, пока мы не подали списки на канал. Увидимся на воде! #Пакрафтинг #Каякинг #Богородское #Тренировки #packrafters #kayaknroll #техника_сплава

🔥4👍31

13 Jun 2026, 09:50 UTC247 viewsread 6 August 2026

В Москве 20 июня пройдет соревнование для пакрафтеров. Мероприятие некоммерческое, можно присоединиться поучаствовать. Подробности в посте ниже. Если нужен пакрафт, то вы знаете где его взять) А если не знаете или забыли, то я напомню) По вопросам аренды пиши @packraft

13 Jun 2026, 09:50 UTC337 viewsread 6 August 2026
Forwarded from @kewlpackPhoto

КолПак 2026 20 июня, Москва - развлекательная гонка пакрафтеров 5 километров пешком, 5 километров на пакрафте Мероприятие некоммерческое, дружеское, преследующее исключительно увеселительные цели для сообщества пакрафтеров. Регистрация - https://forms.yandex.ru/u/6a2d0aadd046886708938c45 Приходите и приглашайте друзей. Подробнее про маршрут: ВНИМАНИЕ - СТАРТ НЕ ТАМ, ГДЕ БЫЛ В 2025 ГОДУ! Старт 20 июня, суббота,

Showing the 8 most recent of 8 posts we hold for @Packrafters_Adventure. 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.

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.

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.

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

“Packrafters.Adventure|Пакрафт-прокат” (@Packrafters_Adventure), 350 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/Packrafters_Adventure.

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.