Telegram RegisterThe public register of Telegram
Telegram profile photo for Красный Лиман Z

Channel

Красный Лиман Z

@KrLimanZ

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

4,975subscribers

+0 since we began measuring on 26 September 2026

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

Register entry

Telegram ID-1001465137030
TypeChannel
Username@KrLimanZ
Description🔹Красный Лиман 🔹Славянск 🔹Краматорск Подпишитесь сейчас и не теряйте связь с родным городом! 🇷🇺 *️⃣ Все посты на данном канале носят исключительно информационный характер
First recorded26 September 2026
Last confirmed live26 September 2026
Measurements held2
On Telegramt.me/KrLimanZ

Growth

4,97526 Sept 2026, 18:47 — 4,975 subscribers26 Sept 2026, 19:22 — 4,975 subscribers26 Sept 2026, 18:4726 Sept 2026, 19:22
2 measurements taken within a single day. 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 4,970–4,980 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 19:224,975no change
26 Sept 2026, 18:474,975first reading

Engagement

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

ERR · 30 days
50.7%
avg views ÷ 4,975 subscribers
Avg views / post
2,520
18 posts measured
Reaction rate
0.905%
reactions ÷ views · ER floor
Posts in window
18
of 18 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 26 September 2026
Posts held18 (8 September 2026 – 26 September 2026)
Views total45,420
Reactions total411
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 19: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.

What this channel posts

Photos
≈6,480
Videos
≈2,950
Links
≈3,680

Lifetime counters from Telegram’s own channel header, read 26 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

411 reactions across 18 posts, in 18 distinct kinds. The most used accounts for 29.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏12129.4%
❤8821.4%
🤬5012.2%
👍368.76%
🔥307.30%
😁276.57%
😢143.41%
☃81.95%
🤔81.95%
❤‍🔥71.70%
🤪61.46%
🎅51.22%
💔30.73%
🥰30.73%
😭20.487%
👎10.243%
💯10.243%
🤯10.243%

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

Measured over the 18 most recent posts we hold, published 8 September 2026 to 26 September 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

26 Sept 2026, 13:29 UTC610 views9 reactionsread 26 September 2026
Photo

Харьковская область. Наши воины освободили нп. Должанка.

❤‍🔥6☃1❤1😁1

25 Sept 2026, 21:52 UTC≈1,180 views33 reactionsread 26 September 2026
Photo

ВСУ заняли район севернее Красного Лимана и продвинулись вдоль Северского Донца до Ямполя. Также скорректирован фронт на Славянском направлении.

🤬24🥰3💔2🤔2☃1😁1

25 Sept 2026, 13:05 UTC≈1,310 views52 reactionsread 26 September 2026

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

🙏45🔥4❤2🤪1

25 Sept 2026, 13:04 UTC≈1,290 views13 reactionsread 26 September 2026
Photo

Харьковская область. Зачистка котла. Наши воины освободили нп. Бузово.

🔥11☃1😁1

24 Sept 2026, 17:39 UTC≈1,550 views42 reactionsread 26 September 2026
Photo

Славянское направление. Враг отбросил наших воинов из Ореховатки. Также противник атакует со стороны Николаевки и смог закрепится на западной окраине нп. Рай-Александровка. Наши воины бьют всем чем есть.

🙏33❤5😁4

23 Sept 2026, 22:12 UTC≈1,650 views14 reactionsread 26 September 2026
Photo

ВС РФ приблизились к городу Белозерское — итоговая сводка Readovka за 23 сентября Пока части 51-й армии продолжают сжимать клещи вокруг гарнизона неприятеля в Доброполье, другая ее часть начала движение в направлении города Белозерское. Сейчас противник сильно ослаблен, что позволяет войскам ВС РФ действовать с большими амбициями. На руку нашим подразделениям играет и погода, мешающая неприятелю использовать дроны.

❤7👍4😁2🙏1

22 Sept 2026, 11:46 UTC≈2,330 views24 reactionsread 26 September 2026
Photo

Алексеево-Дружковка. Наши воины практически полностью освободили юго-западную часть нп. до реки.

❤10🙏10🔥2☃1🤬1

21 Sept 2026, 22:10 UTC≈2,230 views16 reactionsread 26 September 2026
Photo

Краматорское направление. Наши воины закрыли карман в районе нп. Малиновка. Освобождено 9.5 км².

❤9🔥5☃1😁1

20 Sept 2026, 21:52 UTC≈2,530 views25 reactionsread 26 September 2026
Photo

Харьковская область. Наши воины освободили нп. Черное, Нефедовка, Благодатное, Василевка. Котел закрылся. Освобождено 57 км².

👍16🔥5😁2☃1❤1

18 Sept 2026, 21:55 UTC≈2,960 views15 reactionsread 26 September 2026

Николаевка становится «аэродромом» для русских дронов, — итоговая сводка Readovka за 18 сентября Украинский гарнизон вышел из Николаевки точно так же, как из Алексеево-Дружковки, и город – это большая серая зона, где действуют как наша пехота, так и украинская; Противник использует Славянскую ТЭС, изобилующую техническими постройками, села Высокоивановка, Семеновка и Стародубовка в качестве «точек устойчивости» при…

❤5🙏4😁3🤔2👎1

18 Sept 2026, 21:49 UTC≈2,610 views10 reactionsread 26 September 2026
Photo

Дружковское направление. Веролюбовка. Наши воины освободили бо́льшую часть нп.

👍7😁2😭1

17 Sept 2026, 14:36 UTC≈3,400 views17 reactionsread 26 September 2026

⚡️ Армия РФ взяла под контроль населенный пункт Малая Волчья в Харьковской области и Розовку в Запорожской Как сообщает Минобороны РФ, в Харьковской области российские войска продолжают сжимать кольцо окружения, расширять внешнюю зону контроля и пресекают все попытки подразделений ВСУ прорваться из котла.

❤8🙏7☃1❤‍🔥1

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

Новосибирск * Новости * Важное
@Novosibirsk_vajnoe · 26,043
Telegram ranks this channel #9 of 72 here — alongside 71 others — read 26 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“Красный Лиман Z” (@KrLimanZ), 4,975 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/KrLimanZ.

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.