Telegram RegisterThe public register of Telegram
Telegram profile photo for СОКОЛИНОГОРЕЦ

Channel

СОКОЛИНОГОРЕЦ

@sokolinogorez

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

32subscribers

+0 since we began measuring on 20 August 2026

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

Register entry

Telegram ID-1003399133990
TypeChannel
Username@sokolinogorez
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live5 September 2026
Measurements held2
Confirmed unchanged3 times, most recently 5 September 2026
On Telegramt.me/sokolinogorez

Growth

3220 Aug 2026, 12:31 — 32 subscribers20 Aug 2026, 18:46 — 32 subscribers20 Aug 2026, 12:3120 Aug 2026, 18:46
2 measurements taken within a single day. 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 31–33 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Aug 2026, 18:4632no change
20 Aug 2026, 12:3132first reading

Engagement

17 posts held, back to 2 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.

ERR · 30 days
370.8%
avg views ÷ 32 subscribers
Avg views / post
119
3 posts measured
Reaction rate
18.2%
reactions ÷ views · ER floor
Posts in window
3
of 17 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. It is computed over the 1 of 3 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 August 2026
Posts held17 (2 June 202616 August 2026)
Views total356
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 12:31 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
11s
Average length
11s

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.

Reaction mix

22 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1150.0%
👍627.3%
29.09%
👏14.55%
🤯14.55%
🥰14.55%

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

Measured over the 17 most recent posts we hold, published 2 June 2026 to 16 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

16 Aug 2026, 16:59 UTC315 viewsread 20 August 2026

Вот так прошел выездной этап #марафонудома в Коломне. Большое спасибо организаторам, волонтерам и всем кто в этом был замешан, за вкусные угощения (окрошка😍), за душевную компанию, за улыбки, за трассу и за погоду🤗. Смотрите видео, почти ничего не вырезал, желаю всем приятного просмотра на 53 минуты. ВК: https://vkvideo.ru/video-234364448_456239149 Рутюб: https://rutube.ru/video/e69431af9af174bf1763be9976e82ec2/

13 Aug 2026, 11:22 UTC19 viewsread 20 August 2026
Forwarded from @RussianBackyardUltraPhoto

https://www.m24.ru/videos/08082026/928588 ✅Москва 24 "Москва – столица спорта": ультрамарафон на выбывание Russian Backyard Ultra🔥

8 Aug 2026, 18:43 UTC22 views4 reactionsread 20 August 2026
Forwarded from @nearhomemarathonVideo

Август, и, казалось бы, «Вот и лето прошло, Словно и не бывало…». Но пока за окном +25 и солнце, мы не согласны с этим утверждением! Уже в это воскресенье #марафонудома собирает друзей в гостях в Коломне. Солнце, ветер, классный город и крутые ребята вокруг - вот рецепт идеальных выходных. Не знаешь, как добраться до Коломны? Забыл где старт и финиш? - загляни СЮДА. ❗️Обратите внимание! Большинство парковок рядом с

👍21🔥1

27 Jul 2026, 20:41 UTC199 views4 reactionsread 20 August 2026

Вот как прошли мои 19 часов в Битцевском лесу 25-26.07.2026 г. Предлагаю краткое для тех кто не любит долгие фильмы и большое, где я собрал по максимуму информации и отзыв свой и своего сапорта любимой жены. Будет интересно. Конечно, я не заснял змею, которая выбежала ко мне на дорогу, не заснял красные облака, полицию ночью, которая светила в 🫪 глаза в три машины) и много разных разговоров, которые не давали мне оде

👍2🔥1🥰1

24 Jul 2026, 13:29 UTC52 views4 reactionsread 20 August 2026
Photo

Завтра буду штурмовать свой второй Бэкьярд и первый в этом году. 🏃

🔥4

19 Jul 2026, 18:36 UTC96 views1 reactionsread 20 August 2026

Сегодня 19.07.2026 был забег Лента в Парке Культуры. Подготовил видео, длинное и короткое. Тут вставлю короткое на 3 минуты, кому захочется полное видео см на моих каналах. 1) на вк https://vkvideo.ru/video-234364448_456239146 2) на Рутюбе https://rutube.ru/video/e9eeaeac483e6823e5e8b1cf2fec797d/?r=a

👍1

18 Jul 2026, 15:16 UTC150 views3 reactionsread 20 August 2026

Сделал небольшой тизер на 14 минут своей пробежки по Дороге в Лавру, которую совершил 27.06.2026 пробежав в одиночку, может кому-то сложно смотреть 45 минут. В 4 к и под зажигательную мелодию предлагаю Вам окунуться в чудесную пробежку-путешествие длинною в 18 часов и 121 км. См в ВК✅: https://vkvideo.ru/video-234364448_456239142 В Рутюбе✅: https://rutube.ru/video/d29a2be3110c165aa665f6f33524e1e3/

🔥2👍1

30 Jun 2026, 06:37 UTC134 views2 reactionsread 20 August 2026

Пробежал Дорогу в Лавру 27.06-28.06.2026 г.🏃 Стартанул в 6:18, приземлился в 0:21.🐜 Было много всего за 18 часов, вышло на 45 минут, почти ничего не вырезал, сделал только небольшой монтаж.📀 Желаю удачного просмотра в качестве 4к, можно смотреть в телевизоре или на большом мониторе ✅ П.С. Там я много говорил Видео в ВК👀: https://vkvideo.ru/video-234364448_456239141 Видео в Рутюбе👀: https://rutube.ru/video/ff38176d3b9

1🔥1

28 Jun 2026, 08:07 UTC70 views3 reactionsread 20 August 2026
Photo

Пробежал Дорогу в Лавру. Будет чуть позже видео.

🔥2🤯1

21 Jun 2026, 07:47 UTC135 viewsread 20 August 2026

Спасибо организаторам забега На Старт!, который прошёл в нашем округе ВАО на стадионе Авангард🦾 Очень красивая локация, а больше всего понравилась финишная арка❤️ Снял видео как пробежал 10 км и 3 км (с семьёй), награждение (кроме 5км) всех участников и старты всех дистанций и финиши. Качество в 4к и можно смотреть на большом экране 🏃🏃‍♀ В ВК https://vkvideo.ru/video-234364448_456239138 В Рутюбе https://rutube.ru/vid

19 Jun 2026, 06:26 UTC74 viewsread 20 August 2026

В ВК https://vkvideo.ru/video-234364448_456239135 В Рутюбе https://rutube.ru/video/aff33bee9eedfb74c5486e2e3ca6b898/?r=a

14 Jun 2026, 22:08 UTC656 viewsread 20 August 2026

В ВК https://vkvideo.ru/video-234364448_456239134 В Рутюбе https://rutube.ru/video/d626644a5b56d73536d61d9265c64bcf/?r=a

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

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

“СОКОЛИНОГОРЕЦ” (@sokolinogorez), 32 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/sokolinogorez.

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.