Telegram RegisterThe public register of Telegram
Telegram profile photo for VSE HOROSHO

Channel

VSE HOROSHO

@HOROSOVSE

2 usernames

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

491subscribers

+86 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001632757369
TypeChannel
Usernames@HOROSOVSE @vsehorosho
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/HOROSOVSE

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

4054914486 August 2026 — 405 subscribers7 August 2026 — 405 subscribers8 August 2026 — 405 subscribers14 August 2026 — 413 subscribers15 August 2026 — 417 subscribers24 August 2026 — 413 subscribers29 August 2026 — 437 subscribers1 September 2026 — 448 subscribers8 September 2026 — 485 subscribers10 September 2026 — 486 subscribers15 September 2026 — 489 subscribers18 September 2026 — 491 subscribers6 August 202618 September 2026
12 measurements spanning 43 days, net +86. 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 392–504 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 16:19491+2
15 Sept 2026, 13:39489+3
10 Sept 2026, 20:21486+1
8 Sept 2026, 22:00485+37
1 Sept 2026, 03:46448+11
29 Aug 2026, 22:38437+24
24 Aug 2026, 04:17413-4
15 Aug 2026, 20:54417+4
14 Aug 2026, 19:54413+8
8 Aug 2026, 05:46405no change
7 Aug 2026, 00:03405no change
6 Aug 2026, 23:49405first reading

Engagement

20 posts held, back to 20 July 2026the 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 20 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
55s
Average length
28s

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

587 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 47.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
27947.5%
custom 52738792399915276108714.8%
custom 5426907155221455893579.71%
custom 5417946762520317384447.50%
custom 5354920801806066333294.94%
custom 5422538735394766352183.07%
💔183.07%
custom 5431469278073207884172.90%
custom 5353086185050750631132.21%
custom 5370953476635368811111.87%
🐳81.36%
custom 535052794361546402161.02%

Custom emoji. 9 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 19 of the 20 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 587 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 20 July 2026 to 4 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

4 Aug 2026, 17:13 UTC191 views28 reactionsread 8 August 2026
Photo

Я так понимаю многие даже и не видели, что вышел первый видос из путешествия по Турции 🇹🇷 видимо у вас не прожат колокольчик и вас не уведомляет о выходах видео! Смотреть 🐈‍⬛️

custom 5417946762520317384149custom 52738792399915276105

4 Aug 2026, 12:37 UTC201 views20 reactionsread 8 August 2026
Video

Video, posted without a caption

custom 5370953476635368811116custom 52738792399915276102custom 53530861850507506311

3 Aug 2026, 13:20 UTC214 views27 reactionsread 8 August 2026
Photo

Photo, posted without a caption

19custom 52738792399915276106custom 54225387353947663522

2 Aug 2026, 08:09 UTC242 views25 reactionsread 8 August 2026
Video message

Video message, posted without a caption

10custom 52738792399915276108custom 54179467625203173847

2 Aug 2026, 05:57 UTC233 views24 reactionsread 8 August 2026

Мы в ста километрах от границы с Грузией 🇬🇪

10custom 541794676252031738410custom 53505279436154640214

1 Aug 2026, 20:24 UTC227 views31 reactionsread 8 August 2026
Video

Дальше больше! ♥️ https://youtube.com/@trevel144?si=_qBa1OP_XHOES4Wc

12custom 53530861850507506319custom 54179467625203173847custom 53505279436154640212custom 54225387353947663521

1 Aug 2026, 20:17 UTC220 views18 reactionsread 8 August 2026

Скоро пересечем 400 попищиков

custom 54225387353947663529custom 54179467625203173846custom 53530861850507506313

31 Jul 2026, 17:04 UTC242 views33 reactionsread 8 August 2026
Video message

Video message, posted without a caption

16custom 527387923999152761011custom 54225387353947663526

30 Jul 2026, 18:07 UTC280 views51 reactionsread 8 August 2026
Photo

Photo, posted without a caption

30custom 52738792399915276109💔8custom 54314692780732078844

29 Jul 2026, 17:04 UTC299 views41 reactionsread 8 August 2026
Video message

Video message, posted without a caption

19custom 54269071552214558939custom 53549208018060663338custom 52738792399915276105

29 Jul 2026, 12:33 UTC283 views37 reactionsread 8 August 2026
Video message

Video message, posted without a caption

15custom 527387923999152761012custom 542690715522145589310

Showing the 12 most recent of 20 posts we hold for @HOROSOVSE. 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.

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.

ИЖЕВСК СЕГОДНЯ
@izhevsxy · 50,110
Telegram ranks this channel #32 of 54 here — alongside 53 others — read 25 August 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.

“VSE HOROSHO” (@HOROSOVSE), 491 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/HOROSOVSE.

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.