Telegram RegisterThe public register of Telegram

Channel

Только Динамо, не только футбол!

@dinamolifes

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

1,512subscribers

+1 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-1002466054018
TypeChannel
Username@dinamolifes
CreatedBetween 1 September 2024 and 31 March 2025— 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/dinamolifes

Growth

1,5111,5131,5127 August 2026 — 1,511 subscribers7 August 2026 — 1,511 subscribers10 August 2026 — 1,513 subscribers14 August 2026 — 1,512 subscribers7 August 202614 August 2026
4 measurements spanning 7 days, net +1. 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,511–1,513 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:461,512-1
10 Aug 2026, 18:281,513+2
7 Aug 2026, 21:461,511no change
7 Aug 2026, 15:241,511first reading

Engagement

17 posts held, back to 1 August 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
31.0%
avg views ÷ 1,512 subscribers
Avg views / post
469
17 posts measured
Reaction rate
2.58%
reactions ÷ views · ER floor
Posts in window
17
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 16 of 17 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 7 August 2026
Posts held17 (1 August 20267 August 2026)
Views total7,978
Reactions total192
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 21:46 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.

Reaction mix

192 reactions across 16 posts, in 16 distinct kinds. The most used accounts for 31.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52466993297327463426131.8%
custom 52716821494712525352714.1%
🥴2010.4%
157.81%
custom 5287457358191037334147.29%
😭147.29%
🤔84.17%
👍73.65%
custom 526973229874338543252.60%
🌭52.60%
😢52.60%
🥱52.60%
💯21.04%
🤣21.04%
custom 520416620847091692810.521%
😨10.521%

Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 16 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 192reactions 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 1 August 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, 15:33 UTC209 views10 reactionsread 7 August 2026
Photo

Игровые номера новичков команды. Новичков в этом году как то многовато)

custom 52716821494712525359👍1

6 Aug 2026, 17:26 UTC374 views7 reactionsread 7 August 2026

Кажется, рекламного контента с Динамовцами будет много. Даже интересно, что могут рекламировать Шараканов с Никоновым?

custom 527168214947125253561

6 Aug 2026, 14:32 UTC408 views12 reactionsread 7 August 2026

Отличная новость! И заодно привет одному журналисту, который весной писал что Игорь не хочет работать с Тамбиевым.

custom 527168214947125253512

5 Aug 2026, 17:39 UTC425 views25 reactionsread 7 August 2026

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

custom 524669932973274634217👍52🥱1

5 Aug 2026, 17:26 UTC412 views19 reactionsread 7 August 2026

Ну с побеДой!!!!

custom 524669932973274634214custom 52874573581910373344🌭1

5 Aug 2026, 16:22 UTC421 views5 reactionsread 7 August 2026

Очень странные ощущения от первого тайма: вроде и игра идет, мяч до ударов доводим, но штанга, перекладина, прямое попадание во вратаря... Мы это уже видели пару раз в чемпионате...

💯2🥴2custom 52466993297327463421

5 Aug 2026, 15:09 UTC406 views8 reactionsread 7 August 2026

Ждем победу!!!

5custom 52466993297327463423

5 Aug 2026, 07:07 UTC439 views14 reactionsread 7 August 2026
Photo

Старт кубкового турнира в Воронеже - идеальное место для ротации, получения игровой практики тем, кто мало играл на старте чемпионата. Касерес и Зайдензаль скорее всего сыграют по тайму, игроки атаки тоже могут ротироваться, но старт ждем примерно такой. Шанс для тех, кто играет мало или вообще не играл со старта. Верим в команду ждём победу!

custom 524669932973274634284🥱1custom 52874573581910373341

4 Aug 2026, 06:53 UTC418 views24 reactionsread 7 August 2026
Forwarded from @bredfanataPhoto

Фансектора наших сербских братушек 🎫 ФК Нови Пазар - OФК Београд 1:4

custom 524669932973274634212custom 52874573581910373347custom 52697322987433854325

3 Aug 2026, 19:26 UTC495 views14 reactionsread 7 August 2026

Ну и стоило ли убегать из Динамо?

🤔8🌭4🤣2

3 Aug 2026, 16:58 UTC501 views12 reactionsread 7 August 2026

Хм, а насколько правильно проводить автограф-сессию болельщика соперников перед матчем? Даже если это одноклубники

🥴7custom 52874573581910373342👍1😨1custom 52041662084709169281

2 Aug 2026, 16:55 UTC693 views21 reactionsread 7 August 2026
Photo

И снова очень плохие выходные для наших футболистов. Три поражения у команд нашей системы.

🥴11😢5custom 52466993297327463423🥱2

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“Только Динамо, не только футбол!” (@dinamolifes), 1,512 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dinamolifes.

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.