4 measurements spanning 4 days, net -7. 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,356–1,365 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Aug 2026, 21:17
1,357
-5
8 Aug 2026, 16:55
1,362
-2
7 Aug 2026, 22:20
1,364
no change
7 Aug 2026, 18:41
1,364
first reading
Engagement
10 posts held, back to 22 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
6.67%
avg views ÷ 1,357 subscribers
Avg views / post
90.5
10 posts measured
Reaction rate
102.3%
reactions ÷ views · ER floor
Posts in window
10
of 10 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
Window
Rolling 30 days · latest post in window 31 July 2026
Posts held
10 (22 July 2026 – 31 July 2026)
Views total
905
Reactions total
926
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 22:20 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
5m 00s
Average length
33s
Measured directly from 9 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
926 reactions across 10 posts, in 13 distinct kinds. The most used accounts for 28.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
265
28.6%
❤
244
26.3%
🔥
210
22.7%
👏
40
4.32%
🏆
33
3.56%
❤🔥
31
3.35%
✍
29
3.13%
💯
17
1.84%
🕊
15
1.62%
⚡
13
1.40%
🥰
12
1.30%
😁
10
1.08%
🙏
7
0.756%
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 10 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 926reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 22 July 2026 to 31 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.
Telegram Stars
Stars received
10
across the posts below
Posts paid on
10
of 10 we hold a reading for · 100%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tripl3. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 10 most recent posts we hold for this entry, published 22 July 2026 to 31 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
#1000днейспорта
Дни 639-640/1000🦾 // #бег 🏃♂️
#отпуск #цифровойдетокс #пауза
📆: 30-31.07.2026
🌡️: +29°C
📍: Тюмень
👥: @n_naumova
Что ж, друзья, настало время ненадолго с вами попрощаться.
С сегодняшнего вечера мы уезжаем в отпуск на две недели. В то самое место, куда возвращаемся уже много лет. Отдаленное место возле небольшой деревни в глубинке нашей необъятной страны. Настолько удалённое, что там практически нет…
#1000днейспорта
День 638/1000🦾 // #бег
#марафон #трансформация #идентичность
📆: 29.07.2026
🌡️: +32°C
📍: Затюменский парк, Тюмень
У меня официально началась предотпускная суета.
Подбиваю дела по работе, понемногу собираем вещи, всё это смешано с подготовкой к марафону и обильно приправлено поиском бензина и более-менее чистой воды в городе.
Звучит как план. По факту выглядит как маленький апокалипсис😆
Но самое уд…
#1000днейспорта
День 637/1000🦾 // #бег 🏃♂️
#полезнаясреда@Tripl3
#жара #акклиматизация #подготовкакмарафону
📆: 28.07.2026
🌡️: +32°C
📍: Затюменский парк, Тюмень
Честно, во мне сейчас борются две противоположные личности. Одна настаивает на резком снижении объёмов, вторая всё ещё подталкивает к нагрузкам почти как на пиковой неделе, только без высокой интенсивности.
Вчера решил, что истина где-то посередине. Выше…
#1000днейспорта
День 636/1000 🦾 // #бег 🏃♂️
#пикпозади #восстановление #тейпер
📆: 27.07.2026
🌡️: +29°C
📍: Затюменский парк, Тюмень
👥: @n_naumova
Ну что ж, друзья, пик марафонской подготовки официально позади.
Пробежек теперь станет меньше, они будут короче, а главной задачей станет не набрать форму, а сохранить то, что удалось построить за последние месяцы.
За эти пиковые недели я многое упустил из привычной жиз…
#1000днейспорта
День 635/1000🦾 // #бег 🏃♂️
#пиковаядлительная #марафон #подготовка
📆: 26.07.2026
🌡️: +30°C
📍: Затюменский парк, Тюмень
👥: @n_naumova
Пока утром в воскресенье «миллионы тюменцев» (кто местный — поймёт этот локальный мем 😄) готовились праздновать второй день Дня города, мы с Наташей вышли на утреннюю пробежку. "Искупался" в вазелине, натянул символическую футболку Тюменского марафона и погнали.
По …
#1000днейспорта
День 634/1000🦾 // #бег 🏃♂️
#Тюмень #деньгорода #440направильномпути
📆: 25.07.2026
🌡️: +24°C
📍: Тюмень
Вчера Тюмень отмечала 440-летие.
И знаете, этот город для меня давно перестал быть просто местом, где я живу.
Именно здесь случилась моя трансформация.
И я абсолютно уверен, что городская среда сыграла в ней огромную роль.
Именно здесь я познакомился с «5 вёрст», которые стали частью моей жизн…
#1000днейспорта
День 633/1000🦾 // #бег 🏃♂️
#марафон #подготовка #пиковыенедели
📆: 24.07.2026
🌡️: +27°C
📍: Тюмень
Сложный день.
Чувствуется накопленная усталость от повышения недельных объёмов. Пробежки временно перестали приносить привычное удовольствие. Но это не причина их отменять.
Не был уверен, получится ли вечерняя тренировка, поэтому впервые за всю историю моего бега на стадионе решил сделать там длительн…
#1000днейспорта
День 632/1000🦾 // #бег 🏃♂️
#пятничныемысли #дисциплина #жизнь
📆: 23.07.2026
🌡️: +24°C
📍: Тюмень, стадион / зал DDX
👥: @n_naumova
Вчера утром был стадион, а вечером — быстрая интервальная работа на беговой дорожке.
На вечерней тренировке планировал контрольные 33 минуты, но я остановился на двадцать девятой.
Тело очень чётко просигналило: пора остановиться.
И, наверное, это один из главных уроков…
#1000днейспорта
День 631/1000🦾 // #бег 🏃♂️
#дисциплина #марафон #беговыеобъемы
📆: 22.07.2026
🌡️: +23°C
📍: Тюмень
Да уж, неделька выдаётся довольно объёмной по бегу.
Вчера и на утренней тренировке бежалось не совсем легко, а на вечернюю вообще выходить не хотелось. Не то чтобы совсем не хотелось, но было очень волнительно. И не зря — честно, бежалось тяжело.
Организм всё ещё адаптируется к повышению объёмов. Цент…
#1000днейспорта
День 630/1000🦾 // #бег 🏃♂️
#полезнаясреда@Tripl3
#беговое #тренировки
📆: 21.07.2026
🌡️: +25°C
📍: Затюменский парк, Тюмень
Как же немного нужно для абсолютного счастья бегуну.
Просто выйти на пробежку и понять, что травмы нет. 😆
Вчера был именно такой день.
Утренняя спокойная пятёрка прошла по плану, а вот перед вечерней скоростной работой на 10 км я немного тревожился. Именно на ускорениях мен…
👍38❤31✍22🔥10
Showing the 10 most recent of 10 posts we hold for @tripl3. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank
Citation-graph rank — 329,858 of 1,183,361entries 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
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 11 August 2026 — this
entry's latest reading, not the date you are reading this.
“Роман Наумов | Жизнь на полной мощности 🚀” (@tripl3), 1,357 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/tripl3.
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.