Telegram RegisterThe public register of Telegram
Telegram profile photo for Кир в мир | Авторские туры

Channel

Кир в мир | Авторские туры

@kir_v_mir

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Cite this entry

1,140subscribers

-2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001610484472
TypeChannel
Username@kir_v_mir
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/kir_v_mir

Growth

1,1401,1431,141.57 August 2026 — 1,142 subscribers7 August 2026 — 1,142 subscribers14 August 2026 — 1,143 subscribers18 August 2026 — 1,142 subscribers24 August 2026 — 1,141 subscribers30 August 2026 — 1,140 subscribers7 August 202630 August 2026
6 measurements spanning 23 days, net -2. 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,140–1,143 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 08:471,140-1
24 Aug 2026, 10:551,141-1
18 Aug 2026, 01:021,142-1
14 Aug 2026, 21:361,143+1
7 Aug 2026, 23:471,142no change
7 Aug 2026, 18:591,142first reading

Engagement

8 posts held, back to 6 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.62%
avg views ÷ 1,140 subscribers
Avg views / post
75.5
2 posts measured
Reaction rate
10.6%
reactions ÷ views · ER floor
Posts in window
4
of 8 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 7 August 2026
Posts held8 (6 July 20267 August 2026)
Views total151
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:47 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
1m 29s
Average length
45s

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

77 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 26.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2026.0%
👍1924.7%
1823.4%
custom 5292198559704182119911.7%
custom 547191266581730268456.49%
❤‍🔥56.49%
😁11.30%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 8 most recent posts we hold, published 6 July 2026 to 7 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
3
of 6 we hold a reading for · 50%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kir_v_mir. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 8 most recent posts we hold for this entry, published 6 July 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 16:27 UTC63 views7 reactions1 Starread 7 August 2026
Photo

🤩 Навигация по каналу Если вы читаете это, значит вам близки путешествия с содержанием. Я историк, который ушёл из науки, чтобы путешествовать и создавать авторские туры. На моём счету 30+ стран и 70+ регионов РФ, а ещё множество довольных туристов. Но на этом мои отношения с профессией по диплому не заканчиваются. В своих турах я показываю регионы, города, деревни, дома местных, горы, степи и другие локации через с

👍32🔥2

6 Aug 2026, 16:35 UTC88 views9 reactionsread 7 August 2026
Photo

📍#байкалкир На самом деле, уже Урал. Но почему бы не напомнить вам о хештегах. Не зря же я почти не забываю их ставить #северкир А точнее Русский Север. Мурманская, Архангельская области, Ханты и Манси и другое #югкир Мои заметки из южной части нашего мира, где есть море. Индия, Сочи и другое #узбекистанкир Узбекистан — одно из моих любимых восточных направлений, часто пишу о нем #калининградкир Калининградская о

👍5🔥21custom 54719126658173026841

21 Jul 2026, 08:50 UTC194 views19 reactionsread 7 August 2026
Video

Летний Байкал куда приятнее и душевнее зимнего. Байкальский лед не переоценен, но в некоторой степени ценится больше, чем должен. Куда-то же нужно водить туристов по России зимой?) А вот лето есть лето.

🔥10❤‍🔥43custom 52921985597041821192

17 Jul 2026, 16:37 UTC246 views12 reactionsread 7 August 2026

​​Что у нас здесь происходит? • Байкал укомплектован, стартуем послезавтра. Мчу на начальную точку, не без приключений • еще один тур на Алтай с 27 по 31 июля (внезапно?) — тоже Про планы на осень вы знаете из расписания туров (смотрите в закрепе) А вот упоминаний 2027 года здесь еще не было Те, кто в канале давно или изучали программы туров на моём сайте, знают о чём я. Потому что я обещал вернуться в Поморье. И

4👍3custom 52921985597041821193❤‍🔥1😁1

9 Jul 2026, 13:33 UTC275 views14 reactions1 Starread 7 August 2026
Photo

Алтай на низком старте, и поезд уже уехал А этот еще нет) Выезжаем в следующее воскресенье 19 июля в большой насыщенный тур-экспедицию вокруг Байкала. Стартуем в Улан-Удэ, изучаем легендарное озеро со всех сторон и ракурсов, финишируем в Иркутске. В карточках много озерных (и не только, Байкал это еще и горы) видов, а самое главное - программа по дням. Читайте программу, оповещайте бухгалтерию об отпуске и погнали

🔥64custom 52921985597041821194

6 Jul 2026, 10:37 UTC254 views16 reactions1 Starread 7 August 2026
Photo

Чиатура Нужно представить рандомное кавказское живописное ущелье с небольшой горной деревней в его глубине чуть больше чем 100 лет назад. На дне его шумит река, горный орел парит над соседней вершиной, пастух пасет овец, на заднем дворе поспевает виноград. В целом, ничего не происходит. Обычная жизнь где-то в глубинах грузинской Имеретии. На эту идиллическую картину сюда пришла советская власть (после того, как ряд

👍84custom 54719126658173026844

Showing the 8 most recent of 8 posts we hold for @kir_v_mir. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

“Кир в мир | Авторские туры” (@kir_v_mir), 1,140 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/kir_v_mir.

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.