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 16 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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
15 measurements spanning 43 days, net -1. 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,789–1,802 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
18 Sept 2026, 14:36
1,797
-2
13 Sept 2026, 20:38
1,799
-1
10 Sept 2026, 02:59
1,800
+1
4 Sept 2026, 19:17
1,799
-1
1 Sept 2026, 02:33
1,800
+3
28 Aug 2026, 23:14
1,797
+1
25 Aug 2026, 15:42
1,796
+3
22 Aug 2026, 16:27
1,793
+2
19 Aug 2026, 15:03
1,791
+1
16 Aug 2026, 17:28
1,790
-2
13 Aug 2026, 09:45
1,792
-2
9 Aug 2026, 23:36
1,794
-3
7 Aug 2026, 04:46
1,797
-1
6 Aug 2026, 06:51
1,798
no change
6 Aug 2026, 05:07
1,798
first reading
Engagement
10 posts held, back to 16 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 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 10 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
21s
Average length
11s
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
545 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 34.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
186
34.1%
🔥
119
21.8%
🙏
89
16.3%
💔
65
11.9%
😭
46
8.44%
❤🔥
22
4.04%
😎
7
1.28%
💯
6
1.10%
👏
5
0.917%
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 10 of the 10 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 583 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 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.
Закрытая презентация маршрутов 2027 🌄
23 августа в 19:30 по Мск мы проведем ежегодную презентацию маршрутов на следующий сезон. Вести её будут Андрей и Даша Борисовы — наши основатели, альпинисты и горные гиды.
Что будет:
☑️ впервые покажем новые направления и даты на 2027 год;
☑️ откроем спецусловия на бронирование — только для участников;
☑️ разыграем мерч и сертификаты на скидки прямо во время эфира;
☑️ поделимс…
Чтож, к сожалению чуда не случилось…
Жалко всех
А с Нимсом я даже успел познакомиться лично при очень забавных обстоятельствах: я встретил его в окружении каких-то европейских пижонов. Он уже был на очень синих движениях, но при этом уверенно держался на ногах. Я решился подойти пообщаться, а он тогда пожелал мне успехов на Манаслу и сказал, что у меня все обязательно получится, потом просто сказал идти тусить вмест…
Есть вершина Пика Ленина 🔥
У нас отличные новости — наша команда поднялась на первую вершину Пика Ленина (7134 м) в этом сезоне и уже благополучно спустилась в первый лагерь.
Это восхождение выдалось непростым. Команда дождалась подходящего погодного окна, а сама гора в очередной раз напомнила, что требует терпения, подготовки и уважения. Благодаря опыту гидов, слаженной работе и настрою участников вершина была дос…
Каникулы на Ленина завершились нашей сокрушительной победой! Естественно, победой над собой.
1. Завел на гору Рустама. Он год готовился к этому после прошлогодней неудачи и в акурат перед своим ДР поднялся. Горжусь!
2. Матвей взял свой первый 7000м. При этом он портерил и нес грузы: на 6400 на своем горбу поднял 32кг, и это при том что раньше выше эльбруса он не бывал! Так что у нас в команде +1 гид-высотник.
3. Встр…
Showing the 10 most recent of 10 posts we hold for @followborisov. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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
Named by 4 registered channels — 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
0
vacant every time we have ever looked
@followborisov named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@whereiskaiun named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 5 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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.
Музыка 2025 | Лучшая музыка @music_letsgo · 27,927 Telegram ranks this channel #30 of 45 here — alongside 44 others — read 10 September 2026
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.
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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“FOLLOWBORISOV” (@followborisov), 1,797 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/followborisov.
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.
