Telegram RegisterThe public register of Telegram
Telegram profile photo for ИЗЮМ НАШ

Channel

ИЗЮМ НАШ

@izyum_nash

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

1,256subscribers

+6 since we began measuring on 4 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002072149475
TypeChannel
Username@izyum_nash
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live18 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/izyum_nash

Growth

1,2501,2561,2534 September 2026 — 1,250 subscribers4 September 2026 — 1,250 subscribers11 September 2026 — 1,254 subscribers14 September 2026 — 1,255 subscribers18 September 2026 — 1,256 subscribers4 September 202618 September 2026
5 measurements spanning 14 days, net +6. 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,249–1,257 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 13:191,256+1
14 Sept 2026, 16:171,255+1
11 Sept 2026, 09:011,254+4
4 Sept 2026, 22:221,250no change
4 Sept 2026, 21:471,250first reading

Engagement

20 posts held, back to 18 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
114.4%
avg views ÷ 1,256 subscribers
Avg views / post
1,440
19 posts measured
Reaction rate
1.14%
reactions ÷ views · ER floor
Posts in window
19
of 20 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
WindowRolling 30 days · latest post in window 31 August 2026
Posts held20 (18 August 202631 August 2026)
Views total27,299
Reactions total312
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Sept 2026, 22:22 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

332 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 44.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤝14844.6%
🤬11033.1%
😢267.83%
🔥164.82%
👍144.22%
103.01%
😱72.11%
🤔10.301%

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 20 of the 20 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 332 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 18 August 2026 to 31 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

31 Aug 2026, 11:16 UTC879 views13 reactionsread 4 September 2026

Подписчик сообщает о прилётах на Поворотке этой ночью. Пока без подробностей.

🤝7🤬5🤔1

29 Aug 2026, 18:24 UTC≈1,070 views16 reactionsread 4 September 2026

Подписчица уточняет: Вчера было на Поворотке, в молокозавод.

🤝8🤬6😢2

29 Aug 2026, 07:08 UTC≈1,160 views15 reactionsread 4 September 2026

Ночью в районе Поворотки прилетело три КАБа.

🤝8🤬6😢1

28 Aug 2026, 18:02 UTC≈1,240 views16 reactionsread 4 September 2026

Подписчик опровергает данную информацию. Но перебои с электричеством были серьезные. В некоторых районах свет появился к часу ночи, в некоторых — только сегодня к обеду.

🤝9🤬52

28 Aug 2026, 08:15 UTC≈1,450 views16 reactionsread 4 September 2026

В Харькове прилёт по Каравану на Салтовке (возле метро Героев Труда). Сам ТЦ не работал, но рядом заправка, которая могла быть целью. Или что-то нехорошее хранили внутри ТЦ.

🔥6🤬6🤝4

28 Aug 2026, 06:54 UTC≈1,390 views13 reactionsread 4 September 2026

От подписчицы: Вчера 27.06.2026 очень мощно прилетело по РЭС админздание

🤝7🤬5🔥1

28 Aug 2026, 06:54 UTC≈1,350 views18 reactionsread 4 September 2026

Прилетело четыре КАБа в 17-й детский сад. Пострадало множество частных домов вокруг.

🤝7🤬5😢4🔥2

27 Aug 2026, 18:47 UTC≈1,460 views17 reactionsread 4 September 2026

Сегодня во второй половине дня прилетело по Верхнему Посёлку. Сейчас там, а так же в районе ИОМЗа, ЖД рынка, Бараков и т.д. нет электричества. Связь очень плохая или отсутствует.

😢6🤝5🤬3🔥21

27 Aug 2026, 11:16 UTC≈1,430 views16 reactionsread 4 September 2026

В Харькове прилетело по «Эпицентру» возле аэропорта. Это был последний супермаркет данной сети в городе.

🤝8🤬4🔥31

26 Aug 2026, 17:57 UTC≈1,410 views16 reactionsread 4 September 2026

Уточняю информацию. Прилёт был в районе той улицы, и вчера вечером, а не сегодня. Подписчик, поделившийся информацией не совсем корректно объяснил.

🤝9🤬61

26 Aug 2026, 16:51 UTC≈1,210 views16 reactionsread 4 September 2026

Прилёт по улице Комсомольской в Изюме. Повреждены жилые дома.

🤝6🤬5👍4😱1

25 Aug 2026, 11:10 UTC≈1,710 views21 reactionsread 4 September 2026

Боеприпасы сдетонировали в районе железного моста в районе ул. Некрасова, там где двухэтажки. Детонация длилась более часа. На ЖД рынке был сущий кошмар. Взрывы были мощнейшие. У людей на ИОМЗе, Верхнем Посёлке, не говоря уже про другие районы, тряслись стены и окна. Разрушения в эпицентре детонации будут очень серьезными. Я уже не говорю о людях. В очередной раз Изюм захыстылы. Дякуемо.

🤬9🤝4😱4😢21🔥1

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

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.

Купянский район для своих ‼️‼️‼️
@kypyansk · 36,931
Telegram ranks this channel #49 of 78 here — alongside 77 others — read 4 September 2026

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.

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

“ИЗЮМ НАШ” (@izyum_nash), 1,256 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/izyum_nash.

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.