Telegram RegisterThe public register of Telegram
Telegram profile photo for Ⓜ️

Channel

Ⓜ️

@Vgorode_777

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

127subscribers

-1 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-1002118557187
TypeChannel
Username@Vgorode_777
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live21 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/Vgorode_777

Growth

127128127.57 August 2026 — 128 subscribers9 August 2026 — 128 subscribers21 August 2026 — 127 subscribers7 August 202621 August 2026
3 measurements spanning 14 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 127–128 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 23:26127-1
9 Aug 2026, 01:45128no change
7 Aug 2026, 14:54128first reading

Engagement

19 posts held, back to 2 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 19 posts for this entry, the most recent from 8 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 45s
Average length
15s

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

250 reactions across 18 posts, in 17 distinct kinds. The most used accounts for 34.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8634.4%
🔥5421.6%
🥰249.60%
😁145.60%
😍124.80%
custom 5384122430480465807104.00%
🏆104.00%
💘104.00%
custom 527825332058510456583.20%
👍52.00%
41.60%
🐳41.60%
💔31.20%
💯31.20%
👏10.4%
💋10.4%
🤩10.4%

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

Measured over the 19 most recent posts we hold, published 2 November 2025 to 8 July 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
6
across the posts below
Posts paid on
1
of 19 we hold a reading for · 5%
Most on one post
6
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Vgorode_777. 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 19 most recent posts we hold for this entry, published 2 November 2025 to 8 July 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

8 Jul 2026, 07:44 UTC122 views14 reactionsread 9 August 2026
Video

Video, posted without a caption

6😍43🔥1

10 Apr 2026, 10:09 UTC314 views27 reactionsread 9 August 2026
Video

Учеба учебой,а цай по расписанию

12🔥7😁5👍3

16 Mar 2026, 09:31 UTC375 views18 reactionsread 9 August 2026
Video

Video, posted without a caption

8custom 52782533205851045656custom 53841224304804658074

5 Mar 2026, 14:08 UTC287 views12 reactionsread 9 August 2026
Video message

Video message, posted without a caption

🐳43🔥3😁2

12 Feb 2026, 11:24 UTC308 views16 reactionsread 9 August 2026
Video

Эх хорошие были времена на анатомии,когда можно было уснуть спокойно😅

🔥83🥰3👍2

30 Jan 2026, 12:37 UTC320 views22 reactionsread 9 August 2026
Photo

Профессор на связи 😅

🔥8custom 53841224304804658076🥰3🏆2custom 52782533205851045652💋1

31 Dec 2025, 16:32 UTC346 views16 reactionsread 9 August 2026

С Новым годом товарищи 😎

9💘4🔥3

25 Dec 2025, 06:16 UTC434 views11 reactionsread 9 August 2026
Video message

Video message, posted without a caption

9👏1🔥1

25 Dec 2025, 06:06 UTC327 views14 reactionsread 9 August 2026
Video message

Video message, posted without a caption

🔥11💘2🤩1

6 Dec 2025, 01:45 UTC358 views6 reactionsread 9 August 2026

Далекий 95 год🧔🏻‍♂️

🏆3😁3

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

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

“Ⓜ️” (@Vgorode_777), 127 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/Vgorode_777.

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.