Telegram RegisterThe public register of Telegram
Telegram profile photo for IKT Билеты Иркутск

Channel

IKT Билеты Иркутск

@ikt_irk

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

26,602subscribers

-299 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001395771813
TypeChannel
Username@ikt_irk
DescriptionАвиабилеты, туры и путешествия из Иркутска. Это информационный канал. Билеты не продаем Реклама и сотрудничество @iata_travel IKT MAX https://max.ru/ikt_irk РКН: https://vk.cc/cGI7Qn
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/ikt_irk

Topic

Travel — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 4 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@kja_krsk/183857 Aug 2026, 13:07 UTC@ikt_irk/7841 · this entry11 Aug 2026, 02:00 UTC1.004 days
@ikt_irk/7885 · this entry14 Aug 2026, 03:13 UTC@kja_krsk/1847114 Aug 2026, 04:16 UTC1.0063 minutes
@ikt_irk/8061 · this entry3 Sept 2026, 06:17 UTC@kja_krsk/186873 Sept 2026, 07:33 UTC1.0076 minutes
@kja_krsk/1926813 Oct 2026, 01:57 UTC@ikt_irk/8399 · this entry13 Oct 2026, 01:58 UTC1.00under a minute
@ikt_irk/7842 · this entry11 Aug 2026, 03:02 UTC@led_spb/592711 Aug 2026, 08:14 UTC1.005.2 hours
@ikt_irk/7885 · this entry14 Aug 2026, 03:13 UTC@led_spb/594514 Aug 2026, 06:00 UTC1.002.8 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@kja_krsk29 (8/8 hand-verifiable sample passed)1.0043 minutes@kja_krsk (19–10)
@led_spb9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (9–0)
@hkt_bkk10 (8/8 hand-verifiable sample passed)1.002.1 hourseven
@kgd_kenig8 (8/8 hand-verifiable sample passed)1.0019 minutesthis entry (7–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 10 of the 10 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 292 comparable posts for this entry, running 3 August 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_mutual · clone_source, last confirmed 12 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

26,59726,90126,74926,6027 August 202611 November 2026
63 measurements spanning 96 days, net -299. 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 26,551–26,947 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
11 Nov 2026, 15:4626,602-5
9 Nov 2026, 21:2026,607-1
8 Nov 2026, 13:0726,608+7
7 Nov 2026, 04:3026,601+4
6 Nov 2026, 07:1926,597-7
5 Nov 2026, 04:2026,604-2
4 Nov 2026, 04:5626,606-5
3 Nov 2026, 07:4726,611-10
2 Nov 2026, 08:3526,621-9
1 Nov 2026, 07:3926,630-5
31 Oct 2026, 08:1726,635-8
30 Oct 2026, 05:4026,643-14
29 Oct 2026, 02:4026,657-16
28 Oct 2026, 01:5026,673-4
27 Oct 2026, 04:2526,677-4
26 Oct 2026, 04:5926,681-5
25 Oct 2026, 08:2626,686-6
24 Oct 2026, 08:1926,692-7
23 Oct 2026, 11:4526,699-1
22 Oct 2026, 14:4626,700first reading

Engagement

426 posts held, back to 2 August 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 215 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.30%
avg views ÷ 26,602 subscribers
Avg views / post
2,210
164 posts measured
Reaction rate
0.293%
reactions ÷ views · ER floor
Posts in window
164
of 426 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. It is computed over the 143 of 164 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 November 2026
Posts held426 (2 August 2026 – 13 November 2026)
Views total361,981
Reactions total940
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 03:26 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
≈5,040
Videos
≈162
Links
≈3,590

Lifetime counters from Telegram’s own channel header, read 13 November 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.

Video runtime
7m 51s
Average length
19s

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

2,176 reactions across 346 posts, in 37 distinct kinds. The most used accounts for 39.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤85539.3%
😁37117.0%
🔥33315.3%
👍24611.3%
🤣944.32%
😱622.85%
❤‍🔥221.01%
👀160.735%
💯160.735%
👏140.643%
😍140.643%
🙈140.643%
😢130.597%
🤗130.597%
🍓110.506%
😭90.414%
🦄90.414%
💔80.368%
🤔70.322%
🥴70.322%
17 further kinds421.93%

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

Measured over the 426 most recent posts we hold, published 2 August 2026 to 13 November 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.

Advertising

Ad load
4.46%
19 of 426 posts carry an ad marker
Regulatory tokens
19
posts carrying an erid · 12 distinct tokens
Median views · ads
1,860
over 19 measured posts
Median views · rest
2,310
over 407 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2Vtzqvb2VCJ89 November 202610 November 2026
2SDnjepcXnU112 November 202612 November 2026
2VtzquWtmBk112 November 202612 November 2026
2Vtzquh2HC1125 October 202625 October 2026
2Vtzqux596M112 October 202612 October 2026
2Vtzqvy19cw120 August 202620 August 2026
2Vtzqw3SrAq119 October 202619 October 2026
2VtzqwLAbbH131 August 202631 August 2026
2VtzqwLGwzT124 August 202624 August 2026
2VtzqwQdBWW111 November 202611 November 2026
2VtzqwgrM26111 November 202611 November 2026
2VtzqxZGxZs121 October 202621 October 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 426 most recent posts we hold, published 2 August 2026 to 13 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 8 of 164 posts held from the last 30 days (4.88%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

13 Nov 2026, 03:04 UTC277 viewsread 13 November 2026
Photo

Напоминаем про распродажу Нордвинда. Для нас такая Казань: https://clck.ru/3WywZu #KZN @ikt_irk

13 Nov 2026, 02:04 UTC587 views1 reactionsread 13 November 2026
Photo

✈️ А что, если следующее путешествие начнётся с танца? Представьте: вы на отдыхе, играет латиноамериканская музыка, вокруг новые люди, и вам не нужно стоять в стороне. Вы просто выходите танцевать! Бачата — это не только танец, но и возможность знакомиться, общаться, находить друзей и получать впечатления. Причём для этого совершенно необязательно иметь танцевальный опыт. 💃 15 ноября (воскресенье) приглашаем на от…

🔥1

13 Nov 2026, 00:59 UTC814 views2 reactionsread 13 November 2026
Video

ИРКУТСК ✈️ летим во Вьетнам☀️🔥🥰 Вылет 04.12 на 11 ночей🔥 ⚠️95 586₽ на ДВОИХ‼️ Выбирайте отель по ссылке👈 В стоимость включено: 💥прямой авиаперелёт с багажом 💥проживание в отеле 💥страховка 💥трансфер 💥топливный сбор БРОНИРОВАТЬ 👉🏻 @kjatours Менеджер в МАХ

❤1🔥1

12 Nov 2026, 11:09 UTC≈1,310 views1 reactionsread 13 November 2026
Photo

И закончим сегодня таким дежурным Нячангом: https://clck.ru/3WyRFK #NHA @ikt_irk

❤1

12 Nov 2026, 10:05 UTC≈1,410 views2 reactionsread 13 November 2026
Photo

Продолжаем ЖИВЫЕ ЧЕСТНЫЕ ОБЗОРЫ ПУТЕШЕСТВИЙ в канале 👉 https://t.me/mirsiris_travel/389 На этот раз 🇯🇵 ЯПОНИЯ - ближе, чем кажется: ✅ Гуляем по Токио и окрестностям ✅ Разбираемся с метро ✅ Возврашаем Такс Фри по новым правилам ✅ Рассказываю про перелет, отели, достопримечательности и не только 🔥 Полный маршрут со всеми ссылками на гугл мэпс Начинаем обзор 👉 ЗДЕСЬ Меня зовут Ирина. Переходите в канал, подписывайт…

❤2

12 Nov 2026, 09:31 UTC≈1,250 views14 reactionsread 13 November 2026
Photo

Пока все мечтают о Тае и Вьетнаме, мы решили напомнить, что в мире существует Чита. И в неё есть билеты. https://clck.ru/3WyF2y #HTA @ikt_irk

😁14

12 Nov 2026, 08:02 UTC≈1,340 views8 reactionsread 13 November 2026
Photo

Зима ещё не началась, а вы уже можете сделать её хуже. В Якутск от 15 946 ₽. https://clck.ru/3Wy4m9 #YKS @ikt_irk

😁4👍3❤1

12 Nov 2026, 07:02 UTC≈1,480 views1 reactionsread 13 November 2026
Advertisementerid 2SDnjepcXnUPhoto

Оптово-розничный гипермаркет «КанцЛидер» разыгрывает сертификат на 2000👍 Как принять участие: 1️⃣ подписаться на канал «КанцЛидера» в MAX; 2️⃣ нажать кнопку «Участвовать» под конкурсным постом. 3️⃣ пригласить друзей в канал. Победителя определят 15 ноября. Реклама. 12+, ООО «Канцлидер», erid: 2SDnjepcXnU

👍1

12 Nov 2026, 05:00 UTC≈1,540 views11 reactionsread 13 November 2026
Photo

Можно слетать в Ереван на следующей неделе. Вернётесь когда вас отпустят обратно. https://clck.ru/3WxpPw #EVN @ikt_irk

😁7❤3👍1

12 Nov 2026, 03:31 UTC≈1,600 views10 reactionsread 13 November 2026
Photo

Вот так и живём: ждём, когда подешевеет, а когда дешевеет — ждём ещё сильнее. https://clck.ru/3WxmxL #PQC @ikt_irk

😁6🔥3❤1

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

Posts edited after publishing

@ikt_irk edited 6 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
20 August 2026
Most recent edit
10 November 2026

Posts recorded as deleted after publishing

We recorded 95 posts on @ikt_irk as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
9 August 2026
Most recent seen missing
8 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
34

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 9 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.

Names

Channels on the register whose handles appear in this channel's posts.

Билеты в Таиланд и Вьетнам
@hkt_bkk · 91,833
16 posts
KJA Авиабилеты Красноярск
@kja_krsk · 59,027
14 posts
Путешествия из Иркутска 🌐
@lomberg_travell · 1,758
5 posts
Leon_shop_38
@leon_shop_38 · 8,295
3 posts
Билеты из Сибири - Новосибирск, Томск, Омск, Кузбасс, Алтай, Красноярск, Иркутск
@travel_from_siberia · 123,414
3 posts
БИЛЕТЫ: Дальний Восток | Владивосток, Хабаровск, Благовещенск и др.
@bilety_dv · 10,756
2 posts
БИЛЕТЫ: Москва и СПб | Горящие авиабилеты и туры
@bilety_mskspb · 16,168
2 posts
БИЛЕТЫ: Омск
@bilety_omsk · 4,261
2 posts
БИЛЕТЫ: Юг и Кавказ | Сочи, МинВоды, Краснодар, Геленджик, Ставрополь
@bilety_ug · 9,610
2 posts
БИЛЕТЫ: Урал | Екатеринбург, Пермь, Тюмень, Челябинск
@bilety_ural · 22,600
2 posts
KGD Билеты Калининград
@kgd_kenig · 9,246
2 posts
KZN Билеты Казань
@kzn_kazan · 3,598
2 posts
LED Билеты Санкт-Петербург
@led_spb · 10,938
2 posts
РК «Мираж»
@mirage_rest · 699
2 posts
Амар Байкал
@amarbaikal · 665
1 post
Азия Импорт Авто - Авто из Японии, Кореи и Китая под заказ
@AsiaImportAuto · 3,325
1 post
Первая Автоколонна: все автомобили здесь
@autokolonna1 · 331
1 post
БИНАРИО
@Binariorest · 149
1 post
ГРАНД ВОРОТА | Гаражные ворота | Уличные ворота | Иркутск | АЛЮТЕХ
@grandvorota · 21
1 post
IrCity.ru | Новости Иркутска | Байкала | Ангарска | Братска
@ircity_ru · 19,643
1 post
Люль крафтит
@luulcraft · 114
1 post
Ново-Ямской | ВСС ДОМ
@Novo_yamskoy · 653
1 post
Сеть стоматологий "32 Белых"
@stom_32belih · 411
1 post
MILLI MIND | travel
@visa_milli_mind · 9,935
1 post

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

ББ | БЛОГЕРЫ БАЙКАЛА
@blogersirk · 10,697
#1
S7 Air Lounge | Иркутск
@s7lounge_irkutsk · 2,172
#2
Baikal Go - Поехали на Байкал
@baikalgo · 1,807
#3
Макс ПРОНЫРА
@Max_proNbIRA · 1,406
#4
Редакция Иркутска
@irk_edition · 16,007
#5
ОДНИМ СЛОВОМ, @#₽*!
@odno_slovo · 5,174
#6
Иркутск №1
@irk01 · 31,137
#7
Байкалинг | Отдых | Путешествия | Иркутская область | Республика Бурятия
@baykaling · 6,016
#8
Первый Байкальский🦭
@one_baikal · 7,141
#9
Откидач. Иркутск. Сибирь. Россия
@otkidach · 17,013
#10
Иркутский движ
@irk_dvig · 22,093
#11
СЛИВА | ИРКУТСК
@sliva_channel_tg · 7,362
#12
svodka38
@svodka38 · 113,285
#13
Город Иркутск
@admirk · 9,676
#14
IrCity.ru | Новости Иркутска | Байкала | Ангарска | Братска
@ircity_ru · 19,643
#15
Ксю делает медиа
@ksudelaet · 314
#16
Редактор в роуминге
@travelingeditor · 2,311
#17
МАЛЬМ
@malmtv · 2,423
#18
Зоюшка, они долбанулись?
@dolbanulis · 1,854
#19
Чисто гипотетически, Паймышев
@chistogipoteticheski · 909
#20
Афиша Иркутск | Куда сходить?
@afisha_irkutsk38 · 4,995
#21
IRK.ru | Афиша Иркутска
@irkruafisha · 8,024
#22
Братчане ✌️
@bratchane · 11,098
#23
Шишкин лес live⚡️⚡️⚡️
@profshishkin · 7,146
#24
Иркутский блог
@irkblog · 6,203
#25
Кружок
@kruzhok_irk · 1,345
#26
Галерея В. Бронштейна
@vbgallery_irkutsk · 4,945
#27
IRK.ru | Новости Иркутска и Приангарья
@irkru · 22,304
#28
Туда-сюда | Байкал, Сибирь и не только
@antonklimovtg · 1,520
#29
Голос улиц
@golos_irkutsk · 2,310
#30
#кобзевнасвязи
@kobzevii · 81,538
#31
Привет, Иркутск!
@privetirk · 469
#32
ИРКУТЯНЕ
@irktlgr · 3,831
#33
Irkutsk Dj Community
@IrkutskDjCommunity · 711
#34
Мой бизнес | Иркутская область
@mb38ru · 6,480
#35
Диляра Окладникова. Поддержка бизнеса
@dilyara_ro · 2,126
#36
Руслан Болотов
@ruslanbolotov · 8,762
#37
Babr Mash
@babr_mash · 41,924
#38
Аэропорт Красноярск
@kja_inform · 9,766
#39
Гастро Иркутск
@gastro_irk · 1,927
#40
Glagol38
@glagol38 · 1,438
#41
Около Байкала
@OkoloBaikala · 3,674
#42
ТВОЙ ИГУ
@my_isu · 6,070
#43
ФОРУМ БАЙКАЛ 2026
@forumbaikal · 2,716
#44
svodka138
@svodka138 · 52,895
#45
Красный Иркутск
@redirkutsk · 6,325
#46
Иркутск. Бабр. Дальше некуда
@irk_24 · 9,206
#47
Точка Иркутска
@Tochka_Irkutska · 2,726
#48
Иркутская нефтяная компания
@irkutskoilcompany · 11,483
#49
ДТП 38RUS
@irkdtp · 63,559
#50
Телеканал АИСТ | Иркутская область
@aisttvru · 7,743
#51
Ангарск Сегодня | Новости Ангарска
@angarsk_today · 12,051
#52
Бабр. Дальше некуда. Сибирь
@babr24 · 6,866
#53
КрасАвиа
@krasavia_ru · 5,587
#54
НТС | Новости Иркутска и Иркутской области
@nts_irkutsk · 5,821
#55
Куда Иркутск | АФИША📣
@i_138 · 6,469
#56
Иркутск политический
@Irkpolicy · 12,057
#57
ЦСИ Огонь
@ogoncca · 3,855
#58
Видео Салон Иркутск
@videosalonirk · 5,188
#59
Говорит Степанов
@stepanovnm · 21,646
#60
Юля в культуре
@northonfire · 701
#61
Папаша Миднайт
@newspapamidnite · 2,351
#62
Правительство Иркутской области
@irkobl · 10,161
#63
Байкальский писыч
@baikalpisych · 10,448
#64
Искусство действия или Самотворение личности
@iskde · 520
#65
эспрессо мне за воротник
@kat_shank_about_coffee · 2,914
#66
Ангарский Коррупционер
@angarskcorruption · 5,170
#67
Эн+: Энергия дела
@enplusgroup · 9,487
#68
ФАСАДНИК
@fasadnik38 · 1,198
#69
Иркутский дрын
@irkdrin · 1,223
#70
Иркутский дзынь
@irkdzen · 2,726
#71
Байкальский баклан
@sterv38 · 2,243
#72
L Pictures
@LPictures7 · 240
#73
Фестиваль Энергия+
@festenergy · 507
#74
В поле зрения | Иркутск
@vpolezreniyaproekt · 7,521
#75
ФГБУ «Заповедное Прибайкалье»
@zapovednoe_pribaikale · 2,194
#76

Read from Telegram’s recommendation API, most recently 12 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

S7 Airlines
@s7airlines · 287,286
Telegram ranks this channel #6 of 73 here — alongside 72 others — read 10 August 2026
KJA Авиабилеты Красноярск
@kja_krsk · 59,027
Telegram ranks this channel #11 of 80 here — alongside 79 others — read 22 August 2026
Иркутский движ
@irk_dvig · 22,093
Telegram ranks this channel #55 of 90 here — alongside 89 others — read 21 September 2026
svodka38
@svodka38 · 113,285
Telegram ranks this channel #57 of 90 here — alongside 89 others — read 15 August 2026
Сводка 18+
@svodka38irk · 26,656
Telegram ranks this channel #65 of 86 here — alongside 85 others — read 12 September 2026
Иркутск №1
@irk01 · 31,137
Telegram ranks this channel #66 of 93 here — alongside 92 others — read 6 September 2026
Новости Иркутска
@novosti_irkutsk · 21,628
Telegram ranks this channel #67 of 97 here — alongside 96 others — read 22 September 2026
svodka138
@svodka138 · 52,895
Telegram ranks this channel #70 of 83 here — alongside 82 others — read 24 August 2026
Иркутск Live
@liveirkytsk · 23,772
Telegram ranks this channel #74 of 78 here — alongside 77 others — read 17 September 2026
Иркутск Сейчас
@irk1tut · 20,695
Telegram ranks this channel #77 of 80 here — alongside 79 others — read 25 September 2026
IRK.ru | Новости Иркутска и Приангарья
@irkru · 22,304
Telegram ranks this channel #92 of 96 here — alongside 95 others — read 21 September 2026

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

“IKT Билеты Иркутск” (@ikt_irk), 26,602 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/ikt_irk.

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.