Telegram RegisterThe public register of Telegram
Telegram profile photo for HIKEPLAN FEED

Channel

HIKEPLAN FEED

@hikeplan_feed

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

917subscribers

+34 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-1002171590962
TypeChannel
Username@hikeplan_feed
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live31 October 2026
Measurements held12
Confirmed unchanged1 time, most recently 31 October 2026
On Telegramt.me/hikeplan_feed

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 19 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 the other topics.

Growth

8839179007 August 2026 — 883 subscribers8 August 2026 — 883 subscribers15 August 2026 — 887 subscribers23 August 2026 — 897 subscribers30 August 2026 — 904 subscribers9 September 2026 — 912 subscribers16 September 2026 — 910 subscribers30 September 2026 — 915 subscribers10 October 2026 — 916 subscribers17 October 2026 — 915 subscribers24 October 2026 — 916 subscribers31 October 2026 — 917 subscribers7 August 202631 October 2026
12 measurements spanning 85 days, net +34. 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 878–922 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Oct 2026, 22:05917+1
24 Oct 2026, 17:36916+1
17 Oct 2026, 09:59915-1
10 Oct 2026, 19:41916+1
30 Sept 2026, 18:41915+5
16 Sept 2026, 23:40910-2
9 Sept 2026, 01:17912+8
30 Aug 2026, 12:54904+7
23 Aug 2026, 05:44897+10
15 Aug 2026, 06:17887+4
8 Aug 2026, 01:06883no change
7 Aug 2026, 17:52883first reading

Engagement

14 posts held, back to 4 July 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.

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

What this channel posts

Video runtime
2m 23s
Average length
1m 12s

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

260 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 57.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥14957.3%
👍8131.2%
❤2610.0%
👏20.769%
🤩20.769%

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

Measured over the 14 most recent posts we hold, published 4 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
30
across the posts below
Posts paid on
1
of 14 we hold a reading for · 7%
Most on one post
30
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @hikeplan_feed. 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 14 most recent posts we hold for this entry, published 4 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, 07:34 UTC170 views20 reactionsread 8 August 2026
Photo

Обновлена карта, данные ОСМ актуальные на 27 июля. Нанесено больше названий населенных пунктов, областей, регионов - проще ориентироваться. Исправлен баг с отображением морей океанов. В картах для часов все стало крупнее, читабильнее + добавлены изолинии с шагом 10м

👍16❤3🔥1

30 Jul 2026, 14:10 UTC479 views11 reactions30 Starsread 8 August 2026
Video

Отчет о прохождении и фото можно посмотреть тут - https://hikeplan.ru/hikes/a25d6b5c-7e56-470e-aba6-83bf56e09ced/gallery

🔥11

29 Jul 2026, 06:33 UTC458 views30 reactionsread 8 August 2026
Photo

Маршрут прошли, едем домой. Live-трекинг отработал и с часов Amazfit, и с Garmin InReach mini 2. Вот лог лайв трекинга — https://hkpln.com/hikes/a25d6b5c-7e56-470e-aba6-83bf56e09ced/live Версию 2.5.0 китайцы в магазин не выпустили - не понравились им скриншоты 🤷 , дома будем разбираться

🔥23👍6❤1

18 Jul 2026, 13:35 UTC697 views27 reactionsread 8 August 2026
Photo

Мы поехали. Две недели по проекту обновлений не будет. Разве что версия 2.5.0 выйдет в магазине, вероятно в конце следующей недели. За сборами и самим походом можно следить в телеграм-канале (там подключен новый телеграм-бот, можно на нашем примере посмотреть, что это такое и как работает) А можно прямо на сайте. Я включу Live-трекинг с нашего маршрута. Отправлять буду с Garmin InReach и с приложения hikeplan для …

🔥16❤6👍3🤩2

16 Jul 2026, 05:56 UTC606 views6 reactionsread 8 August 2026
Photo

Сборка 2.4.0 вышла в магазине. В ней к сожалению еще есть баг с отображением сохраненных треков. В 2.5.0 баг уже будет исправлен. И вот новая (старая из 1.x.x) фича в 2.5.0 - тап на маркер покажет информацию о нем. Версия 2.5.0 отправлена в магазин - ждем. Сборка доступна донам в ВК и подписчикам Бусти: https://vk.com/wall-226455860_349 https://boosty.to/hikeplan/posts/4db734de-734d-4838-8686-821b81fb561e

👍6

13 Jul 2026, 06:03 UTC657 views33 reactionsread 8 August 2026
Photo

Очередное чумовое обновление - HIKEPLAN пришел в Telegram. Бот + приложение. Сборы в поход часто выглядят так: список снаряжения в одной таблице, маршрут обсуждают в чате, погода — где-то в закладках. За день до выхода никто толком не знает, собран ли рюкзак у соседа и хватит ли группе общего снаряжения. Я постарался вынести всю подготовку к походу в одно место — прямо в вашу группу в Telegram. Теперь к ней можно п…

🔥24👍5❤3👏1

12 Jul 2026, 06:46 UTC508 views22 reactionsread 8 August 2026
Photo

Вы неоднократно предлагали добавить еще одну галку в инвентарь. Чтоб можно было сначала отметить, что хочешь взять, а потом уже что взял. Ну вот добавил. Почти вторая галка, только удобнее. А еще ваш список можете распечатать или отправить себе в Телеграм или в Заметки

🔥15👍5❤2

11 Jul 2026, 10:32 UTC451 views10 reactionsread 8 August 2026

Часто спрашиваете, как в часы отправить свои маркеры - вот инструкция https://hkpln.com/blogs/ru/faq/kak-zagruzit-makery-v-chasy

👍6❤2🔥2

10 Jul 2026, 07:26 UTC431 viewsread 8 August 2026

Потестировал вчера Live-трекинг. Работает нормально. Собрал предпросмотр. В магазине появится недели через 2 (или даже 3 - я уеду в горы) Версия доступна в предпросмотре подписчикам в ВК (https://vk.com/wall-226455860_343) и Бусти (https://boosty.to/hikeplan/posts/b87ff628-fff0-497d-82c4-a38aafb127ad)

9 Jul 2026, 06:54 UTC670 views16 reactionsread 8 August 2026
Photo

Видите бирюзовую точку на дисплее? Подключил лайв-трекинг к часам Amazfit. Конечно это не магия и не спутниковая связь, нужен интернет. Но вполне пригодно для использования, если на маршруте интернет появляется эпизодически. Часы копят точки (интервал записи точки вы настраиваете), как появляется связь, они их разом отправляют. Интервалы отправки вы так же настраиваете от 10 до 180 минут. Бирюзовая точка - трекин…

🔥10👍5❤1

8 Jul 2026, 15:07 UTC723 views20 reactionsread 8 August 2026
Photo

Появилась функция Live-трекинга Если у вас есть Garmin InReach устройство, вы можете подключить его к HIKEPLAN буквально в один клик. Достаточно просто указать ссылку на ваш Garmin Mapshare. Что это дает. 1) Приятный интерфейс, а не как у гармин - из-под топора 2) Возможность зрителям подписаться на ваши обновления и наблюдать за вашим продвижением по маршруту 3) Push- и email- рассылка вашим наблюдателям, если вы …

🔥20

5 Jul 2026, 06:58 UTC662 views19 reactionsread 8 August 2026
Video

Вот так можете делиться. Все что видите и слышите - все настраивается. Ненужные элементы можно скрыть.

🔥13❤5👏1

Showing the 12 most recent of 14 posts we hold for @hikeplan_feed. 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 31 October 2026 — this entry's latest reading, not the date you are reading this.

“HIKEPLAN FEED” (@hikeplan_feed), 917 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/hikeplan_feed.

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.