Telegram RegisterThe public register of Telegram
Telegram profile photo for PROSKI лыжный клуб в Нижнем Новгороде

Channel

PROSKI лыжный клуб в Нижнем Новгороде

@proski_nnov

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

500subscribers

+3 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-1001895338854
TypeChannel
Username@proski_nnov
CreatedBetween 1 November 2022 and 31 August 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/proski_nnov

Topic

Sports — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

4975035007 August 2026 — 497 subscribers8 August 2026 — 497 subscribers16 August 2026 — 500 subscribers23 August 2026 — 503 subscribers30 August 2026 — 501 subscribers15 September 2026 — 500 subscribers7 August 202615 September 2026
6 measurements spanning 39 days, net +3. 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 496–504 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 17:37500-1
30 Aug 2026, 21:16501-2
23 Aug 2026, 09:34503+3
16 Aug 2026, 13:56500+3
8 Aug 2026, 04:19497no change
7 Aug 2026, 16:40497first reading

Engagement

20 posts held, back to 22 July 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.

What this channel posts

Video runtime
3m 36s
Average length
1m 12s

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

123 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 85.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥10585.4%
64.88%
64.88%
👏32.44%
👍21.63%
🥰10.813%

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 11 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 123 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 22 July 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, 11:59 UTC88 views8 reactionsread 8 August 2026
Photo

29 августа командный этап Самая необычная гонка сезона🔥 Команда 2 человека, каждый участник проходит три этапа - бег, лыжероллеры даблполинг, лыжероллеры конек. Длина каждого этапа 1км. Участники передают эстафету после каждого этапа и сменяют друг друга 🏆Отдельный зачет среди мужских, женских и смешанных команд Вы можете собрать свою команду или зарегестрироваться самостоятельно и мы найдем вам напарника До встр

6🔥2

6 Aug 2026, 10:00 UTC102 views10 reactionsread 8 August 2026
Photo

Ваши яркие фото со вчерашнего забега🔥 https://vk.ru/album-228363192_311486397 📸Спасибо лучшему фотографу @krym0v А так же общий зачет Летнего кубка после трех этапов🏆 Напоминаем, что в финальный зачет входит 4 лучших гонки из 5, поэтому даже если вы пропустили один этап, еще можно побороться за высокие места в общем зачете💪

🔥82

5 Aug 2026, 19:45 UTC114 views13 reactionsread 8 August 2026
Photo

Финишные протоколы нашего сегодняшнего забега🔥 Новый интересный формат гонки💪 Поздравляем всех финишеров🥇 С нетерпением ждем следующих стартов🏆

🔥13

5 Aug 2026, 09:56 UTC122 viewsread 8 August 2026
Photo

СТАРТОВЫЕ ПРОТОКОЛЫ СЕГОДНЯШНЕГО ЗАБЕГА🥇 ‼️ Так как возможны ошибки при регистрации, ПРОВЕРЬТЕ СВОЮ ФАМИЛИЮ в стартовых протоколах. Если вас нет в протоколах, напишите нам ‼️ ⏰ РАСПИСАНИЕ: 19:00-19:20 - выдача стартовых номеров 19:30 - старт забега (старт раздельный по порядковым номерам) Внимательно ознакомьтесь со схемой дистанции 📸 После финиша всех участников - объявление результатов, награждение и общее фот

4 Aug 2026, 18:18 UTC139 views8 reactionsread 8 August 2026
Photo

К забегу PROSKI готовы💪 🔥 Регистрация открыта на нашем сайте https://proski-nn.ru/letniy_kubok2026_3 Зарегистрироваться можно до завтра до 12:00 Выдача номеров с 19:00 Старт участников с 19:30 📍Встречаемся на середине Динамовки Ждем вас на старте🏆

🔥5👏3

4 Aug 2026, 10:36 UTC150 views19 reactionsread 8 August 2026
Video

Мы попросили наших спортсменов ответить на пару простых вопросов, чтобы понять главное: ради чего они здесь и за что любят команду PROSKI?😊 Включайте видео! Готовьтесь улыбаться и вдохновляться📹💜

🔥153🥰1

3 Aug 2026, 17:33 UTC161 views19 reactionsread 8 August 2026
Photo

В эту субботу состоялся яркий Ночной забег🏃‍♂️🥇 Наши беговые тренировки не прошли даром и все показали достойные результаты🔥 Поздравляем наших спортсменов💪 И ждем вас в эту среду на этапе Летнего кубка PROSKI - забег на Щелоковском хуторе Регистрация на сайте https://proski-nn.ru/letniy_kubok2026_3 Результаты Ночного забега 10км, мужчины Родин Егор - 37:58 Кузнецов Дмитрий - 38:03 Гурылев Вячеслав - 38:19 Денежки

🔥181

3 Aug 2026, 08:50 UTCviews —

PROSKI лыжный клуб в Нижнем Новгороде pinned a photo

3 Aug 2026, 08:47 UTC163 viewsread 8 August 2026
Photo

Расписание тренировок💪 В среду состоится 3й этап Летнего кубка PROSKI - забег на Щелоковском хуторе Старт в 19:30 🏆Регистрация на нашем сайте https://proski-nn.ru/letniy_kubok2026_3 Участвовать можно даже если вы пропустили предыдущие этапы❗️ 🏃‍♂️ Во вторник проведем легкую подготовительную тренировку перед забегом, посмотрим круг и выберем целевой темп 📍 Место встречи: Щелоковский хутор, стартовая поляна https:/

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

Named by

Channels on the register whose posts name this channel's handle.

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

“PROSKI лыжный клуб в Нижнем Новгороде” (@proski_nnov), 500 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/proski_nnov.

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.