Telegram RegisterThe public register of Telegram

Channel

Young Dipso / 144p

@Young_Dipso

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

233subscribers

+0 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-1002102245271
TypeChannel
Username@Young_Dipso
Description«Голос поколения улиц»🦍
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Young_Dipso

Growth

2337 Aug 2026, 05:03 — 233 subscribers7 Aug 2026, 05:18 — 233 subscribers7 Aug 2026, 05:037 Aug 2026, 05:18
2 measurements taken within a single day. 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 232–234 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 05:18233no change
7 Aug 2026, 05:03233first reading

Engagement

20 posts held, back to 30 April 2026the 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.

ERR · 30 days
60.3%
avg views ÷ 233 subscribers
Avg views / post
141
6 posts measured
Reaction rate
6.29%
reactions ÷ views · ER floor
Posts in window
6
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held20 (30 April 20265 August 2026)
Views total843
Reactions total53
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 05:18 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
187
Videos
100
Links
159

Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

230 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 29.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52943448665311311366729.1%
custom 52288313466583932025423.5%
custom 52962532493497624053414.8%
custom 52695026081873392143314.3%
custom 52897320029357476802310.0%
custom 5253855995083371455156.52%
custom 528963904695856074241.74%

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 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 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 230reactions 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 30 April 2026 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, 20:14 UTC76 views7 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 52943448665311311363custom 52538559950833714552custom 52695026081873392141custom 52897320029357476801

26 Jul 2026, 17:02 UTC174 views13 reactionsread 7 August 2026

Репа там дам теперь

custom 52695026081873392147custom 52288313466583932023custom 52897320029357476803

26 Jul 2026, 17:02 UTC143 views11 reactionsread 7 August 2026
Forwarded from @savakrimskiyPhoto

TRAP DAY // MOSCOW 23.08. Это больше, чем просто концерт. Точка сбора тех, кто живет этой музыкой. Хорошие люди, качественный звук и артисты новой волны, чьи треки все чаще оказываются в плейлистах, а имена — звучат из колонок. Line-up: САВА, Lil Moysi, COLD1, НЕ МЕНЯЕТ, 2DEGAIN, LOCAL G, Young Dipso, ЯRKO, Giatto, THE KOMA PERSON, СВОДКА НОВОСТЕЙ, U$HIRO, ФФАТСОВСКИЙ, KVARTALOV, Flowdilla + SPECIAL GUESTS Twenty O

custom 52943448665311311368custom 52897320029357476802custom 52538559950833714551

17 Jul 2026, 12:37 UTC147 views7 reactionsread 7 August 2026
Forwarded from @yuramnepohuyPhoto

SHALOPAY, BABY BORN - Клубняк

custom 52943448665311311363custom 52288313466583932022custom 52695026081873392142

16 Jul 2026, 19:41 UTC157 views12 reactionsread 7 August 2026
Forwarded from @I45ruPhoto

Photo, posted without a caption

custom 52943448665311311366custom 52695026081873392144custom 52288313466583932022

16 Jul 2026, 19:41 UTC146 views3 reactionsread 7 August 2026

Шарит

custom 52288313466583932021custom 52538559950833714551custom 52943448665311311361

16 Jun 2026, 20:03 UTC306 views6 reactionsread 7 August 2026
Forwarded from @I45ruPhoto

Meepo 145 feat. DAW 145 - TRANSIT Prod: DAW 145 Mix: DAW 145 Послушать на SoundCloud

custom 52943448665311311364custom 52897320029357476802

19 May 2026, 10:37 UTC406 views16 reactionsread 7 August 2026

Бля, обожаю клиентов, которые приходят с треками, сгенерированными нейронкой, чтобы я перебил минус, записал и свел трек. А потом говорят, чтобы это звучало как нейронка... Вопрос: а нахуя тогда что-то делать, блять? 🤷‍♂️ Я не понимаю.

custom 522883134665839320214custom 52538559950833714552

10 May 2026, 09:13 UTC468 views24 reactionsread 7 August 2026
Video

🛫

custom 522883134665839320213custom 52962532493497624055custom 52896390469585607424custom 52897320029357476802

8 May 2026, 22:13 UTC354 views19 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 529434486653113113611custom 52897320029357476805custom 52962532493497624053

8 May 2026, 07:18 UTC283 views3 reactionsread 7 August 2026

Опа опа, слушаем нах

custom 52897320029357476803

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

Citation-graph rank

Citation-graph rank — 401,288 of 1,183,361entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

Named by 8 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.

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

“Young Dipso / 144p” (@Young_Dipso), 233 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Young_Dipso.

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.