10 measurements spanning 8 days, net +87. 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 19,543–19,656 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Aug 2026, 16:03
19,643
+17
14 Aug 2026, 01:55
19,626
+21
12 Aug 2026, 18:33
19,605
+3
11 Aug 2026, 16:34
19,602
+12
10 Aug 2026, 19:14
19,590
+21
9 Aug 2026, 19:32
19,569
+5
8 Aug 2026, 17:44
19,564
+6
7 Aug 2026, 19:55
19,558
+2
7 Aug 2026, 12:00
19,556
no change
7 Aug 2026, 11:49
19,556
first reading
Engagement
131 posts held, back to 6 August 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 20 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
15.9%
avg views ÷ 19,643 subscribers
Avg views / post
3,120
131 posts measured
Reaction rate
0.489%
reactions ÷ views · ER floor
Posts in window
131
of 131 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 118 of 131 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 15 August 2026
Posts held
131 (6 August 2026 – 15 August 2026)
Views total
409,080
Reactions total
1,860
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
15 Aug 2026, 08:29 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
15m 08s
Average length
36s
Measured directly from 25 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
1,860 reactions across 118 posts, in 40 distinct kinds. The most used accounts for 16.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
300
16.1%
🤬
286
15.4%
👍
209
11.2%
💯
202
10.9%
😱
111
5.97%
🤡
102
5.48%
😢
93
5.00%
👎
66
3.55%
🙏
63
3.39%
🖕
50
2.69%
😭
49
2.63%
🔥
43
2.31%
😡
42
2.26%
😁
39
2.10%
🤣
32
1.72%
💩
29
1.56%
🥰
29
1.56%
🤔
23
1.24%
🤯
15
0.806%
👏
13
0.699%
20 further kinds
64
3.44%
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 118 of the 131 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 1,860reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 131 most recent posts we hold, published 6 August 2026 to 15 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.
15 августа планируется подвоз в установленные ёмкости по следующим адресам:
ул. Снегиревская, 16
ул. Снегиревская, 34
ул. Муравьёва, 17
ул. Муравьёва, 57
ул. Чикирисова, 17
ул. Чикирисова, 46
ул. Рослого, 86
ул. Кирова, 2
ул. Кирова, 3-5
ул. Кирова, 6
ул. Кирова, 7
ул. Кирова, 13
ул. Полководческая, 8
ул. Полководческая, 12
ул. Луговцова, 8-10-14
ул. Кирова, 23
ул. Кирова, 22
ул. Кирова, 37
ул. Аравийская, 8
ул. Про…
С 17 по 29 августа в ДНР будет сокращена подача воды
Как сообщили в "Воде Донбасса", в эти дни энергетики будут проводить аварийно-восстановительные работы с отключением подстанций, обеспечивающих работу объектов водоснабжения.
"Без полноценного электроснабжения оборудование не может подавать воду в прежнем объёме. В связи с этим подача воды по ДНР будет сокращена", – сообщили в предприятии.
Ленинский | Предложить…
Нам пишут: "Ул. Пухова, 6а так ничего и не сделано по асфальтированию двора и подъездных дорог. Жители самостоятельно очистили двор от грязи, но это до первого дождя."
Ленинский | Предложить новость
Нам пишут: "Пр. Ленинский, 33, первый подъезд, три месяца течёт канализация в подвале. Многочисленные обращения жильцов в ЖЭК не принесли результата. Вонь стоит ужасная! Антисанитария! В подъезде живут маленькие, грудные дети! Просим принять меры!"
Ленинский | Предложить новость
Местные жители спасли собаку, которая провалилась в 3-метровый колодец на ул. Рослого
Ленинский | Предложить новость
❤54👍18🥰4❤🔥3👏2😍2🤡1😢1
Showing the 12 most recent of 131 posts we hold for @Leninskiytyt. 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
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.
Appears in Telegram’s recommendations for other channels
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.
Типичный Донецк @itsdonetsk · 610,495 Telegram ranks this channel #9 of 65 here — alongside 64 others — read 8 August 2026
ЧП Донецк @chp_donetska · 323,251 Telegram ranks this channel #26 of 66 here — alongside 65 others — read 10 August 2026
АГС_Русского_Донбасса @Ags_Donbass · 194,491 Telegram ranks this channel #60 of 72 here — alongside 71 others — read 11 August 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 August 2026 — this
entry's latest reading, not the date you are reading this.
“Ленинский Тут | Донецк” (@Leninskiytyt), 19,643 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Leninskiytyt.
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.