Telegram RegisterThe public register of Telegram
Telegram profile photo for Янгас

Channel

Янгас

@yungusik

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

224subscribers

-1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001620451001
TypeChannel
Username@yungusik
Created24 February 2022measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live10 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 10 September 2026
On Telegramt.me/yungusik

Growth

2242262258 August 2026 — 225 subscribers8 August 2026 — 225 subscribers24 August 2026 — 226 subscribers1 September 2026 — 224 subscribers8 August 20261 September 2026
4 measurements spanning 24 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 224–226 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 10:58224-2
24 Aug 2026, 20:35226+1
8 Aug 2026, 10:20225no change
8 Aug 2026, 10:04225first reading

Engagement

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

What this channel posts

Video runtime
1m 51s
Average length
22s

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

69 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 27.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52670410378759538271927.5%
custom 52288826414528177771623.2%
1521.7%
custom 5364073651991767978913.0%
🔥811.6%
custom 523810735503129450611.45%
🤩11.45%

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

Measured over the 13 most recent posts we hold, published 24 February 2022 to 5 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

5 Aug 2026, 15:38 UTC90 viewsread 8 August 2026

Приходите к Гришане колоться @grisha_melehov

5 Aug 2026, 15:38 UTC78 viewsread 8 August 2026
Forwarded from @grisha_412Video

Video, posted without a caption

19 Feb 2026, 21:00 UTC926 views5 reactionsread 8 August 2026
File

❗️СТОРИС ДЛЯ ПОДДЕРЖКИ РЕЛИЗА❗️

2custom 52381073550312945061custom 52670410378759538271custom 53640736519917679781

19 Feb 2026, 21:00 UTC≈2,240 views14 reactionsread 8 August 2026
Photo

Янгас - Diamond prod by MOLLYRED, XXYNEXX, ZESTYMAIN rec by JUNGLE RECORDS mix by VISIXN cover by Mshntrp photo by Mshntrp СЛУШАТЬ

🔥84🤩1custom 52670410378759538271

17 Feb 2026, 15:00 UTC≈2,530 views9 reactionsread 8 August 2026
Video

Янгас - #Diamond 20.02 dir/shot/edit by - @mshntrpppp rec by JUNGLE RECORDS mix & master by - @VISIXN prod. by - @MOLLYRED @XXYNEXX, @ZESTYMAIN СЛУШАТЬ ######################

9

26 Sept 2025, 05:48 UTC979 views4 reactionsread 8 August 2026

Мише огромный респект за его работу! Подписывайтесь!

custom 52670410378759538273custom 52288826414528177771

26 Sept 2025, 05:47 UTC874 views4 reactionsread 8 August 2026
Forwarded from @mshntrppppPhoto

сделал визуал для егорчика помидорчика. обложка, сниппет, строис, фотки для карточки музыканта. получилось прикольно, меня кормили чебупиццой. прикрепил обложку и сторку, сниппет выкладывал выше.

custom 52670410378759538272custom 53640736519917679782

25 Sept 2025, 21:01 UTC814 views3 reactionsread 8 August 2026
Video

Сторис для поддержки релиза👆👆👆

custom 52288826414528177772custom 52670410378759538271

25 Sept 2025, 21:00 UTC≈4,060 views7 reactionsread 8 August 2026
Photo

Янгас - CORVETTE prod by Holyquest mix by BodyWax cover by Mshntrp photo by Mshntrp Приятного прослушивания чуваки 🤞 СЛУШАТЬ

custom 52670410378759538274custom 53640736519917679782custom 52288826414528177771

17 Sept 2025, 16:00 UTC791 views6 reactionsread 8 August 2026

ХОЧУ ЧТОБЫ ЭТО БЫЛО ВЕЗДЕ!

custom 52670410378759538273custom 52288826414528177772custom 53640736519917679781

17 Sept 2025, 16:00 UTC≈2,340 views17 reactionsread 8 August 2026
Video

Янгас - #CORVETTE 26.09 dir/shot/edit by - @mshntrpppp mix & master by - @bodywax prod. by - @holyquest ######################

custom 522888264145281777710custom 52670410378759538274custom 53640736519917679783

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

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 2 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.

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.

Новости Йошкар-Олы и Марий Эл
@yoshka_smi · 28,701
Telegram ranks this channel #24 of 29 here — alongside 28 others — read 9 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 1 September 2026 — this entry's latest reading, not the date you are reading this.

“Янгас” (@yungusik), 224 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/yungusik.

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.