Telegram RegisterThe public register of Telegram
Telegram profile photo for Хочешь счастья - иди накуй

Channel

Хочешь счастья - иди накуй

@hudeemv_vmeste

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

2,498subscribers

-22 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001141915773
TypeChannel
Username@hudeemv_vmeste
CreatedBetween 1 July 2016 and 29 February 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/hudeemv_vmeste

Growth

2,4982,5202,5097 August 2026 — 2,520 subscribers7 August 2026 — 2,520 subscribers7 August 2026 — 2,519 subscribers10 August 2026 — 2,515 subscribers17 August 2026 — 2,513 subscribers24 August 2026 — 2,510 subscribers27 August 2026 — 2,504 subscribers30 August 2026 — 2,503 subscribers2 September 2026 — 2,501 subscribers6 September 2026 — 2,498 subscribers7 August 20266 September 2026
10 measurements spanning 31 days, net -22. 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 2,495–2,523 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 22:382,498-3
2 Sept 2026, 07:462,501-2
30 Aug 2026, 04:132,503-1
27 Aug 2026, 11:162,504-6
24 Aug 2026, 12:442,510-3
17 Aug 2026, 14:062,513-2
10 Aug 2026, 17:412,515-4
7 Aug 2026, 12:472,519-1
7 Aug 2026, 09:312,520no change
7 Aug 2026, 09:252,520first reading

Engagement

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

Reaction mix

24 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 54.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52670310434870518841354.2%
custom 5431781500720781493625.0%
custom 5197311131428855039312.5%
custom 541379446115297828228.33%

Custom emoji. Every row above is a 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 3 of the 3 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 24 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 3 most recent posts we hold, published 7 May 2026 to 17 May 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

17 May 2026, 04:25 UTC848 views4 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 52670310434870518844

17 May 2026, 04:25 UTC945 views4 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 51973111314288550392custom 54137944611529782822

7 May 2026, 05:03 UTC958 views16 reactionsread 7 August 2026
Photo

Группа мокрые трусы 18 мая старт Www.Mtclub.shop/products/mt

custom 52670310434870518849custom 54317815007207814936custom 51973111314288550391

Showing the 3 most recent of 3 posts we hold for @hudeemv_vmeste. 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“Хочешь счастья - иди накуй” (@hudeemv_vmeste), 2,498 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/hudeemv_vmeste.

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.