Telegram RegisterThe public register of Telegram
Telegram profile photo for В поисках Шамбалы

Channel

В поисках Шамбалы

@shambalabalaklava

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

1,934subscribers

+18 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-1001846199455
TypeChannel
Username@shambalabalaklava
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/shambalabalaklava

Topic

Local community — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 why it has no browse page of its own yet.

Growth

1,9161,9401,9287 August 2026 — 1,916 subscribers7 August 2026 — 1,916 subscribers10 August 2026 — 1,919 subscribers14 August 2026 — 1,938 subscribers24 August 2026 — 1,940 subscribers27 August 2026 — 1,937 subscribers2 September 2026 — 1,936 subscribers7 September 2026 — 1,935 subscribers12 September 2026 — 1,936 subscribers15 September 2026 — 1,934 subscribers1,9347 August 202615 September 2026
10 measurements spanning 40 days, net +18. 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,912–1,944 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 20:181,934-2
12 Sept 2026, 07:401,936+1
7 Sept 2026, 22:141,935-1
2 Sept 2026, 12:491,936-1
27 Aug 2026, 07:491,937-3
24 Aug 2026, 04:391,940+2
14 Aug 2026, 03:471,938+19
10 Aug 2026, 23:411,919+3
7 Aug 2026, 07:451,916no change
7 Aug 2026, 07:331,916first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
5s
Average length
5s

Measured directly from 1 video 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

61 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 47.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2947.5%
❤‍🔥1626.2%
👍813.1%
custom 521089549880578335046.56%
😍11.64%
🙏11.64%
🤗11.64%
🦄11.64%

Custom emoji. One row above is a 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 count beside it is Telegram’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 11 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 61 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 16 July 2026 to 6 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

6 Aug 2026, 03:49 UTC412 views3 reactionsread 7 August 2026

7.08.26 Пятница 🌀 11:00 Балаклава-Инжир 🧿 🌀 12:00 Инжир-Балаклава🧿 🌀 13:00 Балаклава-Инжир 🧿 🌀 18:00 Инжир-Балаклава🧿 Бронируйте места в комментариях.

3

Signed Михаил Козлов

2 Aug 2026, 13:12 UTC750 views1 reactionsread 7 August 2026

3.08.26 Понедельник 🌀 10:00 Балаклава-Инжир 🧿 🌀 18:00 Инжир-Балаклава🧿 Бронируйте места в комментариях. 🌀В остальное время принимаю индивидуальные заказы. ( Мин. 6 чел.)🧿

1

Signed Михаил Козлов

1 Aug 2026, 11:11 UTC769 viewsread 7 August 2026

2.08.26 Воскресенье 🌀 10:00 Балаклава-Инжир 🧿 🌀 11:00 Инжир-Балаклава🧿 🌀 18:00 Балаклава-Инжир 🧿 отменён 🌀 19:00 Инжир-Балаклава🧿отменён Бронируйте места в комментариях.

Signed Михаил Козлов

1 Aug 2026, 11:09 UTC708 viewsread 7 August 2026
Video

2.08.26 Воскресенье 🌀 12:00-18:00 🧿 Путешествие в Затерянный мир. Зайдём во все гроты и красивые места, больше времени для любимых берегов. Ценность 2000р. Бронируйте места в комментариях.

Signed Михаил Козлов

30 Jul 2026, 08:44 UTC876 views2 reactionsread 7 August 2026

1.08.26 Суббота 🌀 10:30 Балаклава-Инжир 🧿 🌀 11:00 Инжир-Балаклава🧿 🌀 18:00 Балаклава-Инжир 🧿 🌀 19:00 Инжир-Балаклава🧿

2

Signed Михаил Козлов

30 Jul 2026, 07:41 UTC849 views3 reactionsread 7 August 2026

https://yandex.ru/maps?whatshere%5Bpoint%5D=33.60015583021635%2C44.49790171273662&whatshere%5Bzoom%5D=21.0&ll=33.60015583021635%2C44.49790171235077&z=21.0&si=x35ewjbkqy041pdhmefhtxf354 Место посадки в Балаклаве.

👍2❤‍🔥1

Signed Михаил Козлов

27 Jul 2026, 04:01 UTC≈1,100 views2 reactionsread 7 August 2026

31.07.26 Пятница 🌀 13:00-19:00 🧿 Путешествие в Затерянный мир. Зайдём во все гроты и красивые места, больше времени для любимых берегов. 2 места Ценность 2000р.

2

Signed Михаил Козлов

23 Jul 2026, 13:20 UTC≈1,350 viewsread 7 August 2026

31.07.26 Пятница 🌀 11:00 Балаклава-Инжир 🧿 🌀 12:00 Инжир-Балаклава🧿

Signed Михаил Козлов

22 Jul 2026, 10:56 UTC≈1,390 viewsread 7 August 2026

На завтра 23.07 дают дождь, но море вроде нормальное, в смысле без ветра и волн. Пишите если нужен рейс на четверг.

Signed Михаил Козлов

21 Jul 2026, 09:33 UTC≈1,340 views0 reactionsread 7 August 2026

22.07.26 Среда 🌀 11:00 Балаклава-Инжир 🧿 🌀 12:00 Инжир-Балаклава🧿

Signed Михаил Козлов

19 Jul 2026, 16:28 UTC≈1,680 viewsread 7 August 2026

20.07.26 Понедельник 🌀 10:00 Балаклава-Инжир 🧿 🌀 11:00 Инжир-Балаклава🧿

Signed Михаил Козлов

18 Jul 2026, 16:09 UTC≈1,420 views35 reactionsread 7 August 2026
Photo

🧿 Подарок от Хары — Оберег на лодке светит: Путь мой будет чист. https://t.me/Hara_Home

❤‍🔥1510custom 52108954988057833504👍2🤗1🦄1😍1🙏1

Signed Михаил Козлов

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“В поисках Шамбалы” (@shambalabalaklava), 1,934 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/shambalabalaklava.

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.