Telegram RegisterThe public register of Telegram
Telegram profile photo for Красный Иркутск

Channel

Красный Иркутск

@redirkutsk

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

6,352subscribers

+45 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001308098629
TypeChannel
Username@redirkutsk
Created2 December 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live9 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/redirkutsk

Growth

6,3026,3526,3276 August 2026 — 6,307 subscribers6 August 2026 — 6,307 subscribers7 August 2026 — 6,309 subscribers9 August 2026 — 6,302 subscribers12 August 2026 — 6,303 subscribers16 August 2026 — 6,304 subscribers18 August 2026 — 6,310 subscribers22 August 2026 — 6,305 subscribers28 August 2026 — 6,314 subscribers31 August 2026 — 6,319 subscribers3 September 2026 — 6,326 subscribers9 September 2026 — 6,352 subscribers6 August 20269 September 2026
12 measurements spanning 34 days, net +45. 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 6,295–6,360 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 00:596,352+26
3 Sept 2026, 09:146,326+7
31 Aug 2026, 03:136,319+5
28 Aug 2026, 13:446,314+9
22 Aug 2026, 06:066,305-5
18 Aug 2026, 20:436,310+6
16 Aug 2026, 01:536,304+1
12 Aug 2026, 07:276,303+1
9 Aug 2026, 17:226,302-7
7 Aug 2026, 02:076,309+2
6 Aug 2026, 10:306,307no change
6 Aug 2026, 09:496,307first reading

Engagement

22 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.84%
avg views ÷ 6,352 subscribers
Avg views / post
308
5 posts measured
Reaction rate
2.60%
reactions ÷ views · ER floor
Posts in window
5
of 22 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 12 August 2026
Posts held22 (31 July 202612 August 2026)
Views total1,538
Reactions total40
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:18 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
9m 11s
Average length
55s

Measured directly from 10 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

413 reactions across 22 posts, in 24 distinct kinds. The most used accounts for 29.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬12029.1%
💯6515.7%
🏆368.72%
348.23%
👍317.51%
245.81%
🤯235.57%
🔥112.66%
🙈102.42%
🤔102.42%
🎉92.18%
👎81.94%
61.45%
🌚61.45%
🤨61.45%
🤣40.969%
😱30.726%
❤‍🔥10.242%
🍾10.242%
🎃10.242%
4 further kinds40.969%

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

Measured over the 22 most recent posts we hold, published 31 July 2026 to 12 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

12 Aug 2026, 02:33 UTC170 views8 reactionsread 12 August 2026
Photo

Куски бетона откалываются от Глазковского моста и падают на автомобильную парковку. Красный Иркутск

🌚3🤬31😱1

12 Aug 2026, 01:54 UTC242 views4 reactionsread 12 August 2026
Photo

Майнинг в шалаше. В Иркутском районе полицейские и энергетики пресекли деятельность двух нелегальных майнинговых ферм в лесном массиве. Сумма причиненного ущерба превысила 8 миллиона рублей. Все технические устройства изъяты. В настоящее время решается вопрос о возбуждении уголовного дела по статье 165 УК РФ. Красный Иркутск

2👍2

12 Aug 2026, 01:49 UTC245 views4 reactionsread 12 August 2026
Video

Шумные строительные и ремонтные работы запрещено проводить с 21:00 до 8:00. В воскресные и праздничные дни — полный запрет. Исключение: аварийные и спасательные работы. 📍 Иркутск, улица Баррикад, 62/11 Красный Иркутск

4

12 Aug 2026, 01:08 UTC309 views5 reactionsread 12 August 2026
Video

О ситуации с парковкой во дворах. 📍Иркутск, улица Щапова, 4 Красный Иркутск

🤬2🙈2🎃1

11 Aug 2026, 12:28 UTC572 views19 reactionsread 12 August 2026
Video

Вода в реке Ушаковка внезапно помутнела. Вероятно, кто-то сливает туда грязные отходы. Напомним, что Ушаковка неподалеку от этого места впадает в Ангару Красный Иркутск

🤬151🌚1😁1😱1

11 Aug 2026, 00:18 UTC717 views16 reactionsread 12 August 2026
Photo

На иркутских дорогах не расслабишься. 📍Синюшина гора Красный Иркутск

💯14🏆2

10 Aug 2026, 02:35 UTC791 views21 reactionsread 12 August 2026
Photo

Зарастание бурьяном — верный признак обветшалости и упадка. Красный Иркутск

💯19🌚2

10 Aug 2026, 00:16 UTC797 views14 reactionsread 12 August 2026
Photo

Автомобилисты разбивают машины на разрушенном железнодорожном переезде. Старые железнодорожные пути частично демонтированы на подходах к переезду, однако в месте пересечения с автомобильной дорогой рельсы до сих пор лежат и образуют серьезное препятствие для водителей. Эта автодорога часто служит объездом ежедневных пробок на Синюшке и Конева. 📍Иркутск, Свердловский район, улица Аргунова Красный Иркутск

8🤬3🙈2🤣1

9 Aug 2026, 12:02 UTC600 views4 reactionsread 10 August 2026
Video

Главные события недели по версии Правительства Иркутской области. В Бодайбинском районе 3 августа пропал с радаров самолет Cessna 182, выполнявший мониторинг лесных пожаров. Спустя 3 дня экипаж вышел на связь: летчики смогли передать свои координаты, собрав радиостанцию из подручных средств. Двое летчиков находятся в больнице, их жизням ничего не угрожает. Губернатор Игорь Кобзев пообщался с медперсоналом новой Ирк

👍2👎2

9 Aug 2026, 05:32 UTC651 views19 reactionsread 10 August 2026
Photo

С Днем строителя! Красный Иркутск

🏆132🎉2🍾1😱1

8 Aug 2026, 00:33 UTC781 views30 reactionsread 10 August 2026
Video

Новости благоустройства. В микрорайоне Ершовский выполнили асфальтирование сорняковых насаждений. Красный Иркутск

🤬22🏆5🤯21

7 Aug 2026, 00:04 UTC900 views32 reactionsread 10 August 2026
Photo

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

🤬273❤‍🔥1🏆1

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

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

Named by 17 registered channels — 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.

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.

Иркутск №1
@irk01 · 31,297
Telegram ranks this channel #5 of 93 here — alongside 92 others — read 6 September 2026
Новости Иркутска и Области
@irkutsk_smi · 105,379
Telegram ranks this channel #11 of 69 here — alongside 68 others — read 15 August 2026
ВЕСТИ-ИРКУТСК
@vestiirkutsk · 28,088
Telegram ranks this channel #22 of 100 here — alongside 99 others — read 10 September 2026
ДТП 38RUS
@irkdtp · 64,341
Telegram ranks this channel #23 of 90 here — alongside 89 others — read 21 August 2026
#кобзевнасвязи
@kobzevii · 79,388
Telegram ranks this channel #23 of 98 here — alongside 97 others — read 19 August 2026
Приангарские думы
@PRiangarskie · 42,351
Telegram ranks this channel #25 of 99 here — alongside 98 others — read 29 August 2026
svodka38
@svodka38 · 114,320
Telegram ranks this channel #41 of 90 here — alongside 89 others — read 15 August 2026
Babr Mash
@babr_mash · 42,293
Telegram ranks this channel #49 of 99 here — alongside 98 others — read 29 August 2026
svodka138
@svodka138 · 53,583
Telegram ranks this channel #49 of 83 here — alongside 82 others — read 24 August 2026

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

“Красный Иркутск” (@redirkutsk), 6,352 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/redirkutsk.

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.