Channel
@spasiyzkoe
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
979subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002240794470 |
|---|---|
| Type | Channel |
| Username | @spasiyzkoe |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/spasiyzkoe |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 18:23 | 979 | +4 |
| 8 Aug 2026, 00:46 | 975 | no change |
| 7 Aug 2026, 13:03 | 975 | first reading |
8 posts held, back to 18 May 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 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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 8 (18 May 2026 – 4 August 2026) |
| Views total | 194 |
| Reactions total | 39 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 00: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.
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.
228 reactions across 8 posts, in 12 distinct kinds. The most used accounts for 39.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 89 | 39.0% | |
| 🎉 | 47 | 20.6% | |
| 🔥 | 28 | 12.3% | |
| 😱 | 24 | 10.5% | |
| 👍 | 10 | 4.39% | |
| ❤🔥 | 9 | 3.95% | |
| 🤬 | 9 | 3.95% | |
| 🤯 | 8 | 3.51% | |
| 💯 | 1 | 0.439% | |
| 😍 | 1 | 0.439% | |
| 🤔 | 1 | 0.439% | |
| 🤗 | 1 | 0.439% |
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 8 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 228reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 18 May 2026 to 4 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.
💕В этот замечательный летний день отмечает День рождения прекрасная защитница Узкого и Битцевского леса, Наталья!🤩 Наташа, спасибо за твоё неравнодушие, добро и красоту, которые ты несёшь в этот мир! Пусть оно вернётся к тебе стократно!🥰 Желаем тебе только побед во всех твоих делах, добрых людей на жизненном пути, хороших событий и исполнений желаний!❤️ 🌼🍓🍒🌞💗
🎉24❤🔥9❤5😍1
Уважаемые любители Битцевского леса, соседи! 🌲 В минувшие дни «Защита Битцевского леса» провела серию субботников в районе м. Лесопарковая. Работы прошли в субботу, а также в понедельник и среду. 🗓 В этом районе сосредоточено значительное количество борщевика Сосновского. Сейчас главная задача — полностью уничтожить соцветия и семена растения, чтобы остановить его дальнейшее распространение. 🌿🚫 Кроме того, по наше…
❤21
🌳 Друзья, мы ищем активных жителей и инициативные группы из Ясенево и Северного Бутово, которым дорог Битцевский лес в его нынешнем, естественном виде! 🌲 Наша главная цель — общественный контроль за любыми работами в Битцевском лесу. Сейчас мы особое внимание уделяем проекту по строительству флагманской лыжной трассы за МКАД. Вы живёте рядом с лесом, каждый день гуляете в нём и замечаете то, что остаётся незамеченн…
🔥14🤗1
🌿 6 июня волонтёры из партии Зелёные и неравнодушные жители провели субботник в Узком. Было собрано 12 больших мешков мусора, который лежал в этих красивейших местах годами. 🌞Большое спасибо всем, кто принял в этом участие, помог очистить природу и сделать этот мир лучше! 💚
❤30
Друзья! 🌍 Во Всемирный день окружающей среды хотим поделиться важной новостью. 📢 С начала этого года мы совместно с другими инициативными группами проводили масштабную кампанию против незаконного строительства лыжероллерной трассы, которая грозила катастрофическим ущербом Битцевскому лесу 🌲. Было собрано более 5 000 подписей жителей в адрес правительства Москвы 📝. Тысячи обращений в правоохранительные и надзорные ве…
❤20🔥7💯1🤔1
💛Друзья, волонтёры из партии Зелёные хотят провести субботник в Узком, чтобы по возможности убрать в яблоневом саду оставшийся и залежавшийся мусор. 🌞🌿Всех желающих зовём присоединиться и помочь! Это отличная возможность, провести эту субботу в приятной компании, на свежем воздухе, делая очень полезное дело. Пусть лето проходит не зря и не банально😉🍒 💚6 июня в 12.00 встречаемся на Тютчевской аллее, близ Северных во…
👍5❤3
🤯В московском Чертаново для благоустройства привезли грунт с фрагментами захоронений — осколками памятников, облицовочной плиткой, погнутым крестом
😱24🤬9🤯8
Сегодня поздравляем С ДНЕМ РОЖДЕНИЯ нашего инспектора, лесного защитника и просто друга - Сергея Утришского! 🎂🎈🎁🫂 Доблесть, честь, отвага, смелость 💪 — Есть все это у тебя 🫵, С днем рождения, Сережа! 🥳 Береги всегда себя ♥️. Пусть тебя удача любит 🤞, И Господь пускай хранит 🙏, В жизни пусть твоей не будет 🙂↔️ Бед, печали и обид! Мы с днем рожденья в этот час 📆 Тебя сердечно поздравляем! 🎉 Здоровья много, сил запа…
🎉23❤10🔥7👍5
Showing the 8 most recent of 8 posts we hold for @spasiyzkoe. 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.
Citation-graph rank — 779,443 of 1,550,220entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“#СпасиУзкое” (@spasiyzkoe), 979 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/spasiyzkoe.
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.