Telegram RegisterThe public register of Telegram
Telegram profile photo for Гірська відьма ⛰️

Channel

Гірська відьма ⛰️

@girska_vidma

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

1,717subscribers

-45 since we began measuring on 14 September 2026

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

Register entry

Telegram ID-1001960252993
TypeChannel
Username@girska_vidma
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live26 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/girska_vidma

Growth

1,7171,7621,739.514 September 2026 — 1,762 subscribers14 September 2026 — 1,762 subscribers15 September 2026 — 1,761 subscribers26 September 2026 — 1,717 subscribers14 September 202626 September 2026
4 measurements spanning 12 days, net -45. 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,710–1,769 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 16:381,717-44
15 Sept 2026, 13:151,761-1
14 Sept 2026, 13:221,762no change
14 Sept 2026, 12:471,762first reading

Engagement

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

ERR · 30 days
22.0%
avg views ÷ 1,717 subscribers
Avg views / post
377
6 posts measured
Reaction rate
3.09%
reactions ÷ views · ER floor
Posts in window
6
of 6 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 9 September 2026
Posts held6 (9 September 2026 – 9 September 2026)
Views total2,263
Reactions total70
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Sept 2026, 13: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.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4767.1%
💘1420.0%
🕊45.71%
😨45.71%
😍11.43%

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

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

9 Sept 2026, 09:52 UTC357 views11 reactionsread 14 September 2026

Коли дійшли до Гимби, у нас був варіант спуститися в Пилипець і вже звідти добиратися до Воловця. Але ми вирішили повертатися назад, як і йшли - приблизно 16 км в одну сторону. Правда, повертатися через Великий Верх уже зовсім не хотілося, бо сил на той підйом не залишилося 😂 Тому вирішили його обійти. Біля вказівника між Гимбою та Великим Верхом знайшли якусь стежку, яка, як ми думали, просто мала провести нас в …

❤9🕊2

Signed Hhigtenzz

9 Sept 2026, 09:51 UTC329 views8 reactionsread 14 September 2026

Одноденний маршрут з Воловця на 35 км 🏔️ Починали о 3:00 ночі від станції Воловець. Але перед цим ми взагалі не спали, тому так робити я не рекомендую, особливо без нормальної підготовки. Першу частину маршруту йшли через ліс у повній темряві. Чули і лисиць, і ще когось незрозумілого біля нас у кущах. Я там уже чесно з життям прощалась 😂 Потім ще натрапили на собак, тому моментами було трохи страшно. Приблизно на …

❤6🕊2

Signed Hhigtenzz

9 Sept 2026, 09:51 UTC315 views5 reactionsread 14 September 2026
Photo

Photo, posted without a caption

❤4😍1

Signed Hhigtenzz

9 Sept 2026, 09:51 UTC320 views11 reactionsread 14 September 2026
Photo

Сходження на Хомʼяк 🏔️ Цього разу піднімалися на Хомʼяк від КПП, який знаходиться біля повороту на водоспад Женецький Гук, неподалік Татарова та Микуличина. В одну сторону маршрут займає приблизно 7 км. На підйом у нас пішло близько 2 годин, а спустилися приблизно за 1,5 години. Сам маршрут я б не назвала дужеее важким. Більшу частину підйому йдете лісом, причому досить круто. І, якщо чесно, мені було набагато скл…

💘9❤2

Signed Hhigtenzz

9 Sept 2026, 09:47 UTC378 views17 reactionsread 14 September 2026
Photo

Сходження на Парашку 🏔️ Цього разу вирішили піднятися на Парашку зі Сколе. Стартували приблизно о 10:00. Що дуже зручно - маршрут починається практично від залізничної станції Сколе, тому довго шукати, звідки йти, не довелося. На вершину прийшли десь о 13:30. Підйом сам по собі не сказати, що важкий, але він довгий. В одну сторону виходить приблизно 11 км, тому ноги втомлюються саме через тривалість маршруту. Біл…

❤9💘4😨4

9 Sept 2026, 09:28 UTC564 views18 reactionsread 14 September 2026

Привіт! Канал знову змінює формат, тепер тут будуть гори, походи, маршрути і все тому подібне Минулий формат не дуже пішов 🥲 Тому кому цікаво - залишайтесь)

❤17💘1

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

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.

schmalgauzen
@schmalgauzen · 24,024
Telegram ranks this channel #31 of 63 here — alongside 62 others — read 17 September 2026
ЛітЕра (НМТ мова + літ.) 🌾
@literazno · 26,487
Telegram ranks this channel #43 of 84 here — alongside 83 others — read 14 September 2026

This channel appears in 2 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“Гірська відьма ⛰️” (@girska_vidma), 1,717 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/girska_vidma.

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.