Telegram RegisterThe public register of Telegram

Channel

Gesh_spot

@gesh_spot

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

1,147subscribers

+5 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002086921411
TypeChannel
Username@gesh_spot
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/gesh_spot

Growth

1,1421,1471,144.57 August 2026 — 1,142 subscribers7 August 2026 — 1,142 subscribers10 August 2026 — 1,146 subscribers14 August 2026 — 1,147 subscribers7 August 202614 August 2026
4 measurements spanning 7 days, net +5. 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 1,141–1,148 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 13:261,147+1
10 Aug 2026, 19:131,146+4
7 Aug 2026, 23:471,142no change
7 Aug 2026, 17:371,142first reading

Engagement

13 posts held, back to 15 May 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.

ERR · 30 days
38.5%
avg views ÷ 1,147 subscribers
Avg views / post
442
2 posts measured
Reaction rate
4.75%
reactions ÷ views · ER floor
Posts in window
2
of 13 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 July 2026
Posts held13 (15 May 202628 July 2026)
Views total884
Reactions total42
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:47 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
4m 58s
Average length
30s

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

410 reactions across 13 posts, in 11 distinct kinds. The most used accounts for 48.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥19748.0%
7117.3%
❤‍🔥6515.9%
👍5212.7%
🙏122.93%
👏40.976%
😢30.732%
20.488%
🎉20.488%
🤔10.244%
🤩10.244%

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

Measured over the 13 most recent posts we hold, published 15 May 2026 to 28 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

28 Jul 2026, 09:48 UTC421 views17 reactionsread 7 August 2026
Video

К сожалению, тренер отменил сегодняшнюю тренировку по теннису. Если вы очень хотели потренироваться сегодня, то можем поставить вам робота, пишите в комментариях, если понадобится. Также мы установили длинный слэклайн на плоском участке склона, а скоро планируем сделать около 30 метров на высоте со страховкой.

10🔥4😢3

27 Jul 2026, 13:55 UTC463 views25 reactionsread 7 August 2026
Video

Мы пока все еще не нашли постоянного тренера по настольному теннису, но Виталию Кочину удалось организовать тренировку с КМС завтра (28.07) в 18:00. Приходите исправлять свои ошибки и учиться. Просто поиграть во время тренировки не получится.

🔥129👍4

7 Jul 2026, 15:06 UTC790 views29 reactionsread 7 August 2026
Video

Добавили кнопку переключения света в рампе. Раньше это можно было сделать только удаленно или в щитке, теперь кнопка доступна всем. Свет переключается с задержкой, так что не торопитесь тыкать повторно. Свет над теннисным столом включается кнопкой на розетке на дереве. Свет на батуте и на склоне пока все еще включается только удаленно.

👍16🔥10🙏21

23 Jun 2026, 07:40 UTC856 views33 reactionsread 7 August 2026
Video

Обновили страховку в рампе, она все так же регулируется по уровню и позволяет тренироваться более безопасно. Также недавно на батут вернулся тренажер для джибинга. Для прыжков на трубу следует использовать джиб доску snowboarding addiction с твердым основанием, а не с мягким. Прыгать с этой доской без трубы не следует, она больше изнашивает сетку. Также на батуте есть фал для имитации вейкборда, в том числе по фигура

🔥198👍6

9 Jun 2026, 02:23 UTC913 views28 reactionsread 7 August 2026

Сегодня с 15:00 до 18:00 начнутся летние групповые батутные тренировки у @ChisKa16 , записаться можно в директ. На время тренировки батут будет доступен только участникам тренировки. Дальнейшие анонсы будут в чате Спота. Также напоминаем, что мы будем рады, если вы захотите проводить на Споте свои тренировки, например, по йоге, скейту или настольному теннису. Мы не берем комиссию, если вы захотите проводить платные т

🔥18❤‍🔥6🙏31

5 Jun 2026, 07:26 UTC854 views39 reactionsread 7 August 2026
Video

Video, posted without a caption

🔥23❤‍🔥86👏2

5 Jun 2026, 07:25 UTC816 views34 reactionsread 7 August 2026

Мы запускаем комплексную подготовку к зимнему сезону с 8 июня по 20 сентября (15 недель) под руководством инструктора категории А, батутного тренера, участника и призера множества российских и международных соревнований - Кати Успенской. Программа: Батутный фристайл - учимся контролю в воздухе и прокачиваем амплитуду прыжков для парка, фрирайда и беккантри. Отрабатываем базовые элементы и вращения: группировки, сед,

🔥209👍2👏2❤‍🔥1

3 Jun 2026, 07:01 UTC620 views17 reactionsread 7 August 2026
Video

Сегодня мы проводим ежегодную обработку от клещей. Средство Blast 505 заявлено, как безопасное для животных, но мы на всякий случай рекомендуем сегодня с собой собак не брать и дать средству рассеяться. Также обратите внимание, что мы обрабатываем всю территорию Спота и часть соседних участков, но если вы отпускаете питомца гулять, то он может выйти за территорию и все равно подобрать клеща. Благодаря обработке мы уж

👍10🙏6🔥1

1 Jun 2026, 07:22 UTC725 views19 reactionsread 7 August 2026
Video

В посте о победителях фото-видео контеста на именах ссылки на оригинал, а сейчас прикладываем видео сюда. При скачивании оригинала не везде выгружается звук, а у одного видео стоит запрет на скачивание, но выкладываем как есть. Также добавили одно наше любимое видео с начала сезона, не участвовавшее в контесте, так как снято и исполнено командой Спота

❤‍🔥11👍71

31 May 2026, 18:01 UTC754 views49 reactionsread 7 August 2026

Последний день маября - не только день рождения нашей замечательной Кати Успенской, но и время подвести итоги ежегодного онлайн фото-видео контеста длиной в сезон. Сезон получился длинный - с 5 октября по 28 мая, 235 дней. За это время под критерии контеста (отметка\коллаб или упоминание Спота) попало несколько десятков видео, так что выбирать нам не было просто. Опишем критерии, на которые смотрели в видео: - количе

🔥2314❤‍🔥8🎉21🤩1

28 May 2026, 03:34 UTC911 views46 reactionsread 7 August 2026
Video

Сегодня последний день работы зимней части Спота. Обещают дожди, которые окончательно размоют оставшийся снег. Чуть-чуть не дотянули до июня, но с учетом открытия 5 октября, сезон получился достаточно долгим. На днях подведем итоги ежегодного зимнего фото-видео контеста

🔥2911👍6

16 May 2026, 10:32 UTC≈1,070 views41 reactionsread 7 August 2026
Video

На курорте в межсезонье почти ничего не работает, но как будто почти все нужное итак во дворе 😅 Постараемся в ближайшее время также организовать наконец хороший слэк-лайн, а то предыдущие версии были посредственными. Продолжаем мечтать о спонсорах и сноупласте, но пока не можем похвастаться, что кого-то интересуют подобные некоммерческие проекты. Так или иначе, мы продолжим не только мечтать, но и потихоньку улучшать

❤‍🔥24🔥142👍1

Showing the 12 most recent of 13 posts we hold for @gesh_spot. 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 — 224,396 of 1,350,102entries 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

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 2 registered channels — 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.

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

“Gesh_spot” (@gesh_spot), 1,147 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/gesh_spot.

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.