Other / unclassifiable — 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 73% 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.
Growth
44 measurements spanning 80 days, net -41. 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 23,334–23,413 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 44
Measured (UTC)
Subscribers
Change
6 Nov 2026, 05:20
23,343
-11
5 Nov 2026, 05:18
23,354
-3
4 Nov 2026, 04:31
23,357
-6
3 Nov 2026, 00:38
23,363
-3
2 Nov 2026, 00:31
23,366
-7
1 Nov 2026, 01:08
23,373
+2
31 Oct 2026, 00:39
23,371
-7
29 Oct 2026, 21:31
23,378
-7
29 Oct 2026, 00:35
23,385
-2
27 Oct 2026, 23:50
23,387
-3
27 Oct 2026, 02:09
23,390
-2
26 Oct 2026, 00:15
23,392
-3
25 Oct 2026, 01:57
23,395
-5
22 Oct 2026, 23:50
23,400
+5
21 Oct 2026, 23:44
23,395
+2
19 Oct 2026, 21:26
23,393
-11
18 Oct 2026, 23:17
23,404
+9
18 Oct 2026, 01:31
23,395
-3
17 Oct 2026, 04:17
23,398
+3
16 Oct 2026, 02:58
23,395
first reading
Engagement
57 posts held, back to 20 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 82 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
17.5%
avg views ÷ 23,343 subscribers
Avg views / post
4,080
20 posts measured
Reaction rate
4.63%
reactions ÷ views · ER floor
Posts in window
20
of 57 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
Window
Rolling 30 days · latest post in window 5 November 2026
Posts held
57 (20 July 2026 – 5 November 2026)
Views total
81,630
Reactions total
3,781
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Nov 2026, 02: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
Video runtime
3m 14s
Average length
39s
Measured directly from 5 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
8,043 reactions across 57 posts, in 17 distinct kinds. The most used accounts for 51.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
4,143
51.5%
❤
2,854
35.5%
🔥
715
8.89%
✍
157
1.95%
🥰
65
0.808%
😁
38
0.472%
👏
25
0.311%
😢
12
0.149%
😍
11
0.137%
🤗
11
0.137%
☃
5
0.062%
🤯
2
0.025%
🎉
1
0.012%
👌
1
0.012%
🖕
1
0.012%
🤩
1
0.012%
🥱
1
0.012%
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 57 of the 57 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 8,043 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 57 most recent posts we hold, published 20 July 2026 to 5 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.
Recent posts
Telegram’s own ‘edited’ marker: 8 of 20 posts held from the last 30 days (40.0%) 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).
Пару слов про Дубну. Очень приятный, ухоженный город, отмечающий в этом году 70-летие. Понравилась экскурсия про историю города. И еще был мастер-класс, где самостоятельно сделали небольшую мозаику. За 25 минут. 😁 Можете попробовать угадать какая моя 😁.
А сейчас уже движемся в Москву.
Прибываем в Дубну. А вчера вечером была небольшая остановка в городе Мышкин. Приятный совсем небольшой городок с шикарной набережной. Жаль, что практически сразу стемнело. Но ничего не поделать, ноябрь все таки.
В Угличе у нас сегодня была короткая остановка, всего 3 часа. Но в итоге замечательная экскурсия и еще успели полчаса сами пройтись. Очень понравился городок, надо сюда еще раз приехать.
Наша каюта, коротенький обзор. Ускорила немного видео, чтобы покороче было.
И на всякий случай ссылка на нашего организатора круиза, может кому то будет нужно - https://s-cruises.com/cruises/
День в Твери подходит к концу. Через 1,5 часа отплываем в Углич.
Мы были здесь, в Твери, проездом в феврале 2022 года и только пару часов тогда смогли выделить на осмотр. Сегодня же практически весь день в городе - продолжительная экскурсия с очень интересным рассказом гида, потом самостоятельно гуляли. 14 км нашагали с большим удовольствием. Спасибо Тверь, нам всё очень понравилось!
В наше сумасшедшее, скоростное время так здорово замедлиться. Смотреть на медленно проплывающий мимо тебя берег, водную гладь. Очень приятные первые впечатления у меня.
Отправляюсь в небольшое путешествие. Речной круиз 4 дня на теплоходе «Лебединое озеро». Завтра буду в Твери, в среду Углич и Мышкин, в четверг Дубна. В пятницу утром возвращаемся в Москву. Давно с мужем хотели в такое путешествие и наконец получилось.
Всех люблю! ❤️
Вот такой красавец еще постоянный посетитель. Но он редкостный флегматик. Сядет на ветку яблони и минут 10 без движения. Потом слетает за семечкой и опять сидит. Или в кормушке зависнет, типа «папа дома» 🤣
Морозное утро 1 ноября. Подмосковье. Теплая и солнечная осень, которая радовала весь сентябрь и октябрь, похоже всё. Зима близко ❄️❄️❄️
❤120👍49🔥16😢12☃5🥰3😍1
Showing the 12 most recent of 57 posts we hold for @irinakhlebnikova. 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
@irinakhlebnikova edited 1 post 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
5 November 2026
Most recent edit
5 November 2026
Posts recorded as deleted after publishing
We recorded 2 posts on @irinakhlebnikova 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
29 September 2026
Most recent seen missing
28 October 2026
Median time before seen missing
10 days
Seen missing in the last 30 days
1
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.
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.
Read from Telegram’s recommendation API, most recently 18 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.
Кулинарим с Таней 🌸 ЛУЧШИЕ РЕЦЕПТЫ🌿 @kulinarimstanej · 86,037 Telegram ranks this channel #6 of 78 here — alongside 77 others — read 18 August 2026
Дина, Коллекция Рецептов @dinarecipes · 36,303 Telegram ranks this channel #11 of 63 here — alongside 62 others — read 1 September 2026
Кухня с Акцентом @zuriskitchen · 56,993 Telegram ranks this channel #30 of 57 here — alongside 56 others — read 23 August 2026
Dr. Bakers | Академия выпечки @drbakers · 29,659 Telegram ranks this channel #60 of 83 here — alongside 82 others — read 7 September 2026
This channel appears in 4 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 6 November 2026 — this
entry's latest reading, not the date you are reading this.
“Ирина Хлебникова” (@irinakhlebnikova), 23,343 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/irinakhlebnikova.
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.