Channel
@kod_Jizny
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
376subscribers
+3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001584491118 |
|---|---|
| Type | Channel |
| Username | @kod_Jizny |
| Created | 3 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/kod_Jizny |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:15 | 376 | +3 |
| 6 Aug 2026, 20:33 | 373 | no change |
| 6 Aug 2026, 12:00 | 373 | first reading |
9 posts held, back to 10 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 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 27 July 2026 |
|---|---|
| Posts held | 9 (10 July 2026 – 27 July 2026) |
| Views total | 4,707 |
| Reactions total | 27 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 20:33 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.
42 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 35.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 15 | 35.7% | |
| ❤ | 13 | 31.0% | |
| 🙏 | 9 | 21.4% | |
| 🕊 | 3 | 7.14% | |
| 👍 | 1 | 2.38% | |
| 👏 | 1 | 2.38% |
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 42reactions 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 10 July 2026 to 27 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.
АНГЕЛЫ ДОНБАССА В Москве почтили память погибших детей Донбасса: цветы, игрушки и минута молчания В столице прошла памятная акция, посвящённая детям, погибшим в результате вооружённого конфликта в Донбассе. В церемонии приняли участие представители Благотворительного фонда «Код Жизни», АНО «Музыка добрых дел», общественные деятели, добровольцы и жители Москвы. Участники возложили цветы и игрушки к мемориалу, почтили…
❤3🙏2
Первые шаги под водой: прошло второе занятие проекта «Дайвинг для героев»24 июля 2026 года состоялось второе занятие проекта «Дайвинг для героев», реализуемого при поддержке регионального гранта совместно с Благотворительным фондом «Код Жизни» и дайвинг-центром «ОКеан».После знакомства с основами дайвинга и изучения теории участники специальной военной операции впервые приступили к практическим занятиям в бассейне. Д…
🔥4🕊3
«Когда поле объединяет людей»: как Благотворительный фонд «Код Жизни» принял участие в празднике «День Тульского поля» 24 июля 2026 года в селе Верхоупье Воловского района Тульской области прошел ежегодный аграрный праздник «День Тульского поля» — одно из крупнейших событий региона, посвященное развитию сельского хозяйства, современным технологиям и достижениям агропромышленного комплекса. Но этот день стал не тольк…
🔥4👏1
https://dobro.press/dobro-media/blogi/%E2%9D%A4%ef%b8%8f-pomogat-znachit-byt-ryadom ❤️ Помогать — значит быть рядом – Добро.Медиа
❤2
Первые шаги к новым глубинам 18 июля 2026 года состоялось первое занятие для участников специальной военной операции, организованное в рамках реализации регионального гранта совместно с Благотворительным фондом «Код Жизни» и дайвинг-центром «ОКеан».Первые шаги к новым глубинам Этот день стал началом большого пути — пути к восстановлению, преодолению внутренних барьеров и знакомству с удивительным миром подводной реа…
🔥5🙏1
⚡⚡⚡ Открыт набор в две команды по киберспорту проекта «Новая миссия»⚡⚡⚡ Благотворительный фонд «Код Жизни» совместно с XP Академией киберспорта объявляет о формировании двух первых команд участников нового социального проекта «Новая миссия». Дисциплины CS2 и DOTA 2 Это проект для тех, кто готов сделать следующий шаг после тяжелых испытаний, найти единомышленников, обрести новые знания, открыть для себя новые возмо…
❤2
Поможем оборудовать Командный пункт на Запорожском направлении! 🇷🇺 Открываем сбор на 4 морских контейнера (20 футов) для оборудования командно-наблюдательных пунктов на позициях наших бойцов. 📦 Стоимость одного контейнера — 55 000 рублей. 🎯 Общая цель сбора — 220 000 рублей. Военнослужащие самостоятельно приедут и заберут контейнеры. От нас требуется только помочь с их приобретением. Каждый контейнер — это защище…
🙏3
Иногда помощь измеряется не только тоннами доставленного груза, километрами пройденных дорог или количеством переданных вещей. Иногда она измеряется надеждой, которая приходит вместе с людьми, не оставшимися равнодушными к чужой беде. Именно таким стал совместный гуманитарный проект, объединивший усилия религиозных организаций, благотворительных фондов и добровольческих объединений ради одной общей цели — поддержать…
❤6🔥2👍1
РАБОТАЙТЕ БРАТЬЯ 10 лет назад, в июле 2016 года, Дагестан потерял своего сына — лейтенанта полиции Магомеда Нурбагандова, убитого боевиками. Намного позже мир узнал имя человека, который даже перед лицом смерти остался верен своим принципам и присяге. 10 июля 2016 года боевики напали на лейтенанта полиции и его родственников, которые отдыхали на природе. Спустя время силовики нашли в телефоне одного из боевиков ви…
🙏3
Showing the 9 most recent of 9 posts we hold for @kod_Jizny. 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 — 357,617 of 1,481,306entries 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.
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.
@kod_Jizny named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“КОД ЖИЗНИ Благотворительный фонд” (@kod_Jizny), 376 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/kod_Jizny.
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.