Channel
@svoi_v_gorakh
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,766subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001501092508 |
|---|---|
| Type | Channel |
| Username | @svoi_v_gorakh |
| Created | Between 1 July 2021 and 31 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/svoi_v_gorakh |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 09:59 | 3,766 | -1 |
| 10 Sept 2026, 20:17 | 3,767 | +2 |
| 5 Sept 2026, 21:16 | 3,765 | +3 |
| 2 Sept 2026, 01:55 | 3,762 | -3 |
| 30 Aug 2026, 02:07 | 3,765 | +3 |
| 27 Aug 2026, 12:38 | 3,762 | -5 |
| 24 Aug 2026, 14:14 | 3,767 | -3 |
| 20 Aug 2026, 22:38 | 3,770 | -5 |
| 17 Aug 2026, 12:47 | 3,775 | +4 |
| 14 Aug 2026, 14:16 | 3,771 | +5 |
| 11 Aug 2026, 10:54 | 3,766 | +11 |
| 8 Aug 2026, 06:11 | 3,755 | -1 |
| 7 Aug 2026, 12:33 | 3,756 | first reading |
4 posts held, back to 4 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 3 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 4 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
188 reactions across 4 posts, in 7 distinct kinds. The most used accounts for 36.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5420325057710815710 | 68 | 36.2% | |
| 🔥 | 43 | 22.9% | |
| custom 5422346595737828862 | 29 | 15.4% | |
| custom 5422483918727183665 | 18 | 9.57% | |
| custom 5422404229903973613 | 15 | 7.98% | |
| 🐳 | 8 | 4.26% | |
| custom 5420408508925376194 | 7 | 3.72% |
Custom emoji. 5 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 are 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 4 of the 4 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 188 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 4 August 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.
Долина реки Кичкинекол в Узунколе⛰ Поход к Турьему озеру на высоту 3080 метров над уровнем моря, с набор высоты от альплагеря более 1000 метров 🚗 И эти виды точно стоят всех усилий!
custom 542032505771081571032custom 542248391872718366517custom 542234659573782886213custom 54204085089253761947
✨ 12 августа, среда Ночной концерт и Звездопад Персеиды А что, если отправиться на природу, чтобы слушать музыку и наблюдать за звездопадом? В эту ночь мы объединим сразу два события: концерт под открытым небом и пик звездопада Персеиды. Для нас выступит it takes 22 — яркий вокал Айсель, гитара Стаса, любимые каверы в акустическом звучании. Проведём вечер вдали от городских огней, под звёздным небом, где музыка ст…
🔥16custom 542240422990397361311custom 542032505771081571010custom 54223465957378288622
На воскресенье, если хотите присоединиться и у вас есть свой сап, можно его взять - стоимость прогулки будет на 1000₽ дешевле. Этим летом такая прогулка будет всего один раз - мы будем купаться в чистой горной реке, прыгать с тарзанки, завтракать на берегу и выйдем в море 🛶 🟧9 августа, воскресенье На сапах по реке Пшада и морю 4300₽ / 3300₽ ➡️по всем вопросам и бронированиям писать @svoivgorakh
custom 542032505771081571015🐳8custom 54224042299039736134
Альплагерь «Узункол» - настоящая легенда Кавказа🏡 Он расположен на высоте около 2100 метров над уровнем моря, в Карачаево-Черкесии, у подножия грандиозных вершин района Гвандра. Отсюда начинаются десятки маршрутов к ледникам, перевалам и вершинам, высота которых достигает почти 4000 метров. История Узункола началась ещё в 1936 году, когда альпинисты впервые начали активно осваивать этот район. А сам альплагерь был …
🔥27custom 542234659573782886214custom 542032505771081571011custom 54224839187271836651
Showing the 4 most recent of 4 posts we hold for @svoi_v_gorakh. 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.
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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Свои В ГОРАХ | походы и путешествия в горы” (@svoi_v_gorakh), 3,766 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/svoi_v_gorakh.
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.