Telegram RegisterThe public register of Telegram
Telegram profile photo for Что-то снимаю в Сочи | блог фотографа и гида 📸

Channel

Что-то снимаю в Сочи | блог фотографа и гида 📸

@snimayuvsochi

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

679subscribers

+9 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001998713878
TypeChannel
Username@snimayuvsochi
CreatedBetween 1 November 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/snimayuvsochi

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 20 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 why it has no browse page of its own yet.

Growth

6706866787 August 2026 — 670 subscribers8 August 2026 — 670 subscribers15 August 2026 — 680 subscribers23 August 2026 — 682 subscribers31 August 2026 — 686 subscribers10 September 2026 — 684 subscribers19 September 2026 — 679 subscribers6797 August 202619 September 2026
7 measurements spanning 43 days, net +9. 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 668–688 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 07:19679-5
10 Sept 2026, 07:35684-2
31 Aug 2026, 13:54686+4
23 Aug 2026, 12:44682+2
15 Aug 2026, 03:48680+10
8 Aug 2026, 02:33670no change
7 Aug 2026, 11:30670first reading

Engagement

5 posts held, back to 22 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 page 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

55 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3563.6%
🔥814.5%
👍712.7%
❤‍🔥23.64%
🥰23.64%
😍11.82%

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

Measured over the 5 most recent posts we hold, published 22 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.

Recent posts

7 Aug 2026, 07:50 UTC95 views5 reactionsread 8 August 2026
Photo

Что нас ждёт 15-16 августа, один из самых красивых хайков этого лета! ❤️‍🔥

3❤‍🔥2

7 Aug 2026, 07:50 UTC95 views1 reactionsread 8 August 2026
Photo

Выкладываю анонсы на ближайшие даты, группы активно набираются, остаётся всё меньше мест! 9 августа, прогулка по хребту Аибга, панорамные виды на горы России и Абхазии. 7000 рублей 13 августа, Табунная, пик Бзерпи, закат в горах. 7500 рублей 15-16 августа, ночь в горах на зеркальном озере, прогулка на пики Ачишхо, Ачипсинские водопады. 14.000 рублей

1

6 Aug 2026, 12:22 UTC117 views17 reactionsread 8 August 2026
Photo

Смотрите какая красота была на последнем хайке на гору Табунная и пик Бзерпи ❤️‍🔥

8🔥7🥰2

28 Jul 2026, 10:25 UTC296 views7 reactionsread 8 August 2026
Photo

2 августа (воскресенье) пойдём по самому живописному маршруту Красной Поляны ❤️‍🔥 Места ещё есть, идём в формате фотохайкинга, на маршруте делаю вам классные фотографии 📷 Все фотографии в посте с этого маршрута (гора Табунная, пик Бзерпи) Пишите в лс: @roma_ph

5👍1🔥1

22 Jul 2026, 16:50 UTC345 views25 reactionsread 8 August 2026
Photo

Фотографии из моего фотохайкинга на хребет Аибга ❤️‍🔥 Вы даже не представляете, что вы теряете хотя бы раз не побывая в горах: – провести день без связи и хотя бы немного очистить свою голову от всяких мыслей – увидеть своими глазами краснокнижную серну (горную козочку) – поесть хот-доги на высоте 2500 метров над уровнем моря – получить прекрасные фотографии и узнать много всего нового о своём регионе, в уникальном

18👍6😍1

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

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Что-то снимаю в Сочи | блог фотографа и гида 📸” (@snimayuvsochi), 679 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/snimayuvsochi.

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.