Короткий сбор в Терсколе подходит к концу! Скоро посмотрим, сколько километров набегали тут. В один из дней сгонял на велике до Тырныауза и обратно в Азау. Получилось с кайфом!
❤18👍7🔥1😈1
Signed Андрей Федоров

Channel
@fedorov_na_sporte
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
499subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002020651115 |
|---|---|
| Type | Channel |
| Username | @fedorov_na_sporte |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/fedorov_na_sporte |
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 72% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 08:37 | 499 | -1 |
| 7 Sept 2026, 18:37 | 500 | +1 |
| 22 Aug 2026, 15:11 | 499 | -1 |
| 8 Aug 2026, 04:18 | 500 | no change |
| 7 Aug 2026, 18:31 | 500 | first reading |
9 posts held, back to 7 July 2026 — the 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 9 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
333 reactions across 9 posts, in 14 distinct kinds. The most used accounts for 40.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 134 | 40.2% | |
| ❤ | 116 | 34.8% | |
| 👍 | 23 | 6.91% | |
| 👏 | 18 | 5.41% | |
| 😱 | 16 | 4.80% | |
| 🤣 | 6 | 1.80% | |
| 🥰 | 6 | 1.80% | |
| 💯 | 4 | 1.20% | |
| 😁 | 3 | 0.901% | |
| 🏆 | 2 | 0.601% | |
| 😈 | 2 | 0.601% | |
| ⚡ | 1 | 0.3% | |
| 🎃 | 1 | 0.3% | |
| 👻 | 1 | 0.3% |
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 9 of the 9 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 333 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 7 July 2026 to 6 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.
Короткий сбор в Терсколе подходит к концу! Скоро посмотрим, сколько километров набегали тут. В один из дней сгонял на велике до Тырныауза и обратно в Азау. Получилось с кайфом!
❤18👍7🔥1😈1
Signed Андрей Федоров
ОСТОРОЖНО! Ненормативная лексика! Видео называется - "в двух словах о ГРУТ Т80" 😬🙈
😱13🤣6💯4👏1
Signed Андрей Федоров
продолжение гонки... В такую погоду что-то менять из снаряжения не имеет смысла, всё мокрое и грязное. Хватаю пачку гелей, пару бутылок воды и быстро убегаю - идеально, первый! Рядом бежит Влад Левин, он несколько лет прибегает на этой дистанции четвёртым. Появился азарт! Говорю Владу - давай, сваливаем от остальных, пока есть просвет. В лесу мы хорошо ориентируемся и может получится сделать отрыв. Добавляю темп. Че…
🔥31❤26🥰5👏2😈1
Signed Андрей Федоров
Golden Ring Ultra Trail 2026 Как это было 😬 Один из самых больших трейловых фестивалей в России прошёл на выходных. Больше десяти тысяч участников за три дня. Куча дистанций - детские, эстафеты, ночная десятка, экстремальные 30 км. Ну и в последний день - основные гонки, Т10-30, Т50, Т80 и сотка Т100. Ещё в мае я решил - попробовать летом дистанцию подлиннее, этакий важный старт. На пятьдесят километров зарегался мо…
🔥22❤16👏5🎃1🥰1😱1
Signed Андрей Федоров
Восемьдесят шесть километров на Golden Ring Ultra Trail Пробежал четыре дня назад 🙈 Днём расскажу - как это было 🙏
🔥35❤9👍4😱2
Signed Андрей Федоров
Мои три падпищика спрашивают, что по завтракам? 😬 Утром питаюсь как на фото. Немного белка - омлет, сырники. Хочется побольше, но тогда на тренировке будет тяжесть в животе (она и так есть!). "Немного зелени" для лучшего усвоения, но здесь нюанс. Обычно утром я не ем зелень, чтоб лучше усвоились углеводы. В итоге общее потребление клетчатки маленькое, с этим приходится бороться). Углеводы - каша рисовая, овсяная, на…
❤15🔥6😁3
Signed Андрей Федоров
Двойной сбор Кисловодск-Архыз 2026 Кончились первые сорок летних дней). Много силовой работы в зале, много МПК интервалов, несколько приличных длительных. Велотренировки теперь в кайф! Спасибо @shulz_strida ☺️ Двадцать девять часов и тринадцать километров набора высоты - только на велике! Тест на беговой дорожке в Кисловодске я провалил. Долго не могли поправить датчик пульса, а когда получилось - я уже устал это …
🔥20❤19🏆2👍2⚡1
Signed Андрей Федоров
День отдыха вот такой получился 😬 Остался последний микроцикл сбора @shulz_strida
👏10👍6❤3👻1
Signed Андрей Федоров
Вчера у тебя не сгибается спина, а сегодня ты делаешь отличную длительную 😬 Такие сборы 🤌 Сгоняли из Архыза до Обсерватории и обратно @shulz_strida pulstime.ru
🔥19❤10👍4
Signed Андрей Федоров
Showing the 9 most recent of 9 posts we hold for @fedorov_na_sporte. 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.
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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Федоров на спорте” (@fedorov_na_sporte), 499 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/fedorov_na_sporte.
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.