Telegram RegisterThe public register of Telegram
Telegram profile photo for ОПАХРЕВШИЕ сапфест

Channel

ОПАХРЕВШИЕ сапфест

@opahrevshie

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

126subscribers

-1 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-1002373146472
TypeChannel
Username@opahrevshie
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/opahrevshie

Growth

126127126.57 August 2026 — 127 subscribers9 August 2026 — 127 subscribers15 August 2026 — 126 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net -1. 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 126–127 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 12:04126-1
9 Aug 2026, 02:01127no change
7 Aug 2026, 16:43127first reading

Engagement

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

What this channel posts

Video runtime
1m 51s
Average length
28s

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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1940.4%
👍1838.3%
😭510.6%
36.38%
👏24.26%

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 10 of the 12 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 47reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 2 January 2026 to 4 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

4 Feb 2026, 18:35 UTC277 views4 reactionsread 9 August 2026

Ребятки наши САПанутые, всем привет!!! В связи с лютыми морозами, которые давно длятся и не планируют заканчиваться, мы не найдем в нашем округе открытую воду! Лед очень плотный, он точно не растает. Поэтому мы вынуждены вас предупредить, что ОПАХРЕВШАЯ МАССЛЕННИЦА, как бы нам ни хотелось, на грани отмены.

😭4

Signed Ruslan Khaziev 116

14 Jan 2026, 09:20 UTC368 views5 reactionsread 9 August 2026

Наши САПанутые друзья, приветствуем вас! В 20х числах января будет информация о предстоящем масленичном заплыве оПахревшая масленица. Ориентировочная дата проведения 21 февраля! Вся подробная информация в ТГ: t.me/clubsuprano/373

🔥5

Signed Ruslan Khaziev 116

7 Jan 2026, 07:36 UTC339 views6 reactionsread 9 August 2026
Forwarded from @len_mosoblVideo

Жители Ленинского округа приняли участие в фестиваль сап-серфинга «Опахревший Новый год». Несмотря на морозный воздух и бодрящую температуру воды, десятки любителей активного отдыха приняли участие в этом необычном мероприятии. Участники соревновались в скорости, креативности костюмов и умении балансировать на сапе. 🏆Победители получили ценные призы и подарки. #ЛенинскийОкруг #ЗимаВПодмосковье

👍3🔥3

Signed Ruslan Khaziev 116

7 Jan 2026, 07:34 UTC253 views3 reactionsread 9 August 2026

https://vesti-vidnoe.ru/news/75258/?ysclid=mk3ot4pzek715847960

👍3

Signed Ruslan Khaziev 116

7 Jan 2026, 07:34 UTC207 views6 reactionsread 9 August 2026
Forwarded from @DSCherkasovPhoto

Сегодня в Ленинском городском округе прошел первый зимний сап-фестиваль «Опахревший Новый год». Место проведения мероприятия как обычно было на реке Пахре в селе Ям, у Каменного Ямского моста. Участники спустились на воду, чтобы преодолеть заплыв, протяженностью 5 километров. Яркие и оригинальные костюмы добавили фестивалю незабываемые впечатления, а их авторы награждены памятными призами. Выражаю благодарность орган

👍6

Signed Ruslan Khaziev 116

5 Jan 2026, 15:42 UTC382 views13 reactionsread 9 August 2026
Video

Вместо весла ледоруб😂

🔥7👍32😭1

Signed Ruslan Khaziev 116

5 Jan 2026, 14:23 UTC400 views3 reactionsread 9 August 2026
Video

Video, posted without a caption

👏2👍1

Signed Ruslan Khaziev 116

5 Jan 2026, 14:22 UTC318 views4 reactionsread 9 August 2026
Video

Video, posted without a caption

🔥4

Signed Ruslan Khaziev 116

5 Jan 2026, 11:43 UTC200 views2 reactionsread 9 August 2026

Точка на карте 55.491611,37.751406 https://yandex.ru/navi/?whatshere%5Bzoom%5D=19&whatshere%5Bpoint%5D=37.751406,55.491611&si=eeqk1rxpa4hd7ufcf439ppcc80 Точка стартового городка! Начало в 12.00

👍2

Signed Ruslan Khaziev 116

5 Jan 2026, 11:10 UTC217 viewsread 9 August 2026
Video message

Video message, posted without a caption

Signed Ruslan Khaziev 116

2 Jan 2026, 17:26 UTC171 viewsread 9 August 2026
Forwarded from @sup_dmd

Ребятки, в связи с переносом "оПахревшего" Новогоднего феста, просим пройти опрос по участникам на 6.01🏄‍♀️🤝 Открытый опрос 👉 t.me/clubsuprano/51

Signed Ruslan Khaziev 116

2 Jan 2026, 12:38 UTC≈3,920 views1 reactionsread 9 August 2026
Photo

Друзья, вода на Пахре встала, из-за погодных условий перенос мероприятия на 6 января. Наши сапанутые друзья, всех вас мы приглашаем на новогодний фестиваль сап-серфинга "Опахревший Новый год" 6го января. Подарки за лучший Новогодний костюм🏄‍♀️ Всем участникам памятные медали🥇 Положение феста и регистрация по ссылке supdmd.ru/opahrevshie Организаторы: Сапсообщество t.me/sup_dmd Сапсообщество t.me/clubsuprano Адм

1

Signed Ruslan Khaziev 116

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

Citation-graph rank

Citation-graph rank — 853,653 of 1,549,376entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“ОПАХРЕВШИЕ сапфест” (@opahrevshie), 126 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/opahrevshie.

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.