Telegram RegisterThe public register of Telegram
Telegram profile photo for Russian Travel Geek

Channel

Russian Travel Geek

@russiantravelgeek

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

4,341subscribers

+227 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001212755649
TypeChannel
Username@russiantravelgeek
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/russiantravelgeek

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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

4,1144,3414,227.57 August 2026 — 4,114 subscribers7 August 2026 — 4,114 subscribers8 August 2026 — 4,217 subscribers11 August 2026 — 4,279 subscribers15 August 2026 — 4,301 subscribers18 August 2026 — 4,320 subscribers22 August 2026 — 4,328 subscribers25 August 2026 — 4,334 subscribers28 August 2026 — 4,322 subscribers30 August 2026 — 4,324 subscribers2 September 2026 — 4,326 subscribers6 September 2026 — 4,333 subscribers11 September 2026 — 4,336 subscribers15 September 2026 — 4,341 subscribers7 August 202615 September 2026
14 measurements spanning 39 days, net +227. 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 4,080–4,375 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 12:194,341+5
11 Sept 2026, 10:194,336+3
6 Sept 2026, 17:574,333+7
2 Sept 2026, 13:144,326+2
30 Aug 2026, 23:494,324+2
28 Aug 2026, 05:284,322-12
25 Aug 2026, 02:584,334+6
22 Aug 2026, 02:044,328+8
18 Aug 2026, 10:064,320+19
15 Aug 2026, 07:464,301+22
11 Aug 2026, 17:134,279+62
8 Aug 2026, 07:034,217+103
7 Aug 2026, 09:014,114no change
7 Aug 2026, 08:534,114first reading

Engagement

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

What this channel posts

Video runtime
3m 35s
Average length
1m 12s

Measured directly from 3 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

166 reactions across 6 posts, in 9 distinct kinds. The most used accounts for 37.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6237.3%
❤‍🔥4728.3%
😁1810.8%
💯137.83%
🦄116.63%
🍓74.22%
👍31.81%
🔥31.81%
😍21.20%

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 166 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 16 July 2026 to 8 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

8 Aug 2026, 06:23 UTC326 views26 reactionsread 8 August 2026
Video

Совсем недавно мы вернулись из нашей микробиологической экспедиции по Камчатке. Все вместе ждём какими данными порадует нас кафедра микробиологии биофака МГУ (чтобы порадоваться за научные итоги экспедиции и научный путь Валеры Лисуна) и плавно разгребаем фотографии (чтобы порадоваться самим и порадовать вас). Короче, сплошные радости. А на кадрах – одна из лекций в термальных источниках, где мы в роли экстремофилов…

❤21👍3🍓1😁1

6 Aug 2026, 15:35 UTC743 views25 reactionsread 8 August 2026
Video

Экспедиция за сокровищами древних эпох в палеосердце Сахары, каково это? 🦕 Это охота за девонскими аммоноидеями, прячущиеся в слоях панцирные рыбы, самурайско-трилобитовое варенье, крепкий марокканский чай, звёзды пустыни сокрытые песком, отпечатки морских звезд под ногами, силурийские морские лилии, кости динозавров в ваших руках и стирка огнём. 😎 Это много чего. И, главное, это замечательные гиды: палеонтолог Я…

❤‍🔥16❤6🔥3

18 Jul 2026, 10:51 UTC≈1,220 views28 reactionsread 8 August 2026
Photo

Новости из мира нейронаук – учёные определили профессии значительно снижающие риск деменции. ⠀ Неврологи Гарварда проанализировали данные представителей около 400 профессий и опубликовали результаты в British Medical Journal. Результат однозначен: реже всего от болезни Альцгеймера страдают люди, сталкивающиеся с необходимостью постоянной навигации и поиска новых дорог. Например таксисты и водители скорой помощи. Увер…

🦄10❤‍🔥8💯8❤2

17 Jul 2026, 11:50 UTC973 views32 reactionsread 8 August 2026
Video

– А на маршруте будет связь? – Будет хорошо. – Да это понятно. А со связью что? – Б у д е т . Х о р о ш о . #russiantravelgeek

😁17❤8🍓6💯1

17 Jul 2026, 06:44 UTC979 views23 reactionsread 8 August 2026
Photo

Вот динозавры планировали-планировали продолжение мирового господства, а в итоге сейчас на ветвях чирикают да яичницей на завтраки нас обеспечивают. Или пакицеты (такие пёсикообразные хищники) гуляли себе по мелководьям да еду высматривали, думали, что так и будут властелинами прибрежных зон. Прошло 50 миллионов лет. Хоп! У них теперь нос на затылке, спать нельзя, а то утонешь, ещё и туристы буквально на спину с селф…

❤‍🔥19💯4

16 Jul 2026, 07:01 UTC893 views32 reactionsread 8 August 2026
Photo

«Да у нас тут знаешь, вулкан, зачастую, ближе чем магазин». 🌋 RTG вновь на Камчатке. Проверяются фальшаки и сублиматы. Закупаются шоколадки. Взвешиваются крупы. Сегодня ещё и в дирекцию природных парков «Вулканы Камчатки» заехали разрешения получить и за развитие территорий пообщаться. Короче, работа кипит. Совсем скоро мы вновь будем забарывать джетлаг на берегу Тихого Океана. А наутро снова ступим под сень каменн…

❤25❤‍🔥4😍2🦄1

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

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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“Russian Travel Geek” (@russiantravelgeek), 4,341 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/russiantravelgeek.

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.