Telegram RegisterThe public register of Telegram

Channel

ASHY 43 💢

@ashytg

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

1,143subscribers

+4 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-1001210717962
TypeChannel
Username@ashytg
Created26 November 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/ashytg

Growth

1,1391,1431,1417 August 2026 — 1,139 subscribers7 August 2026 — 1,140 subscribers10 August 2026 — 1,139 subscribers13 August 2026 — 1,143 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net +4. 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 1,138–1,144 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 10:381,143+4
10 Aug 2026, 04:111,139-1
7 Aug 2026, 11:281,140+1
7 Aug 2026, 03:011,139first reading

Engagement

10 posts held, back to 6 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
35.9%
avg views ÷ 1,143 subscribers
Avg views / post
410
7 posts measured
Reaction rate
12.6%
reactions ÷ views · ER floor
Posts in window
7
of 10 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 6 August 2026
Posts held10 (6 July 20266 August 2026)
Views total2,873
Reactions total362
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03:01 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.

Reaction mix

552 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 40.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 522006366913983718722440.6%
custom 521984981842320393313825.0%
custom 533717374353593420610218.5%
custom 52197039570388639938815.9%

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 10 of the 10 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 552reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

6 Aug 2026, 12:58 UTC183 views34 reactionsread 7 August 2026
Photo

В понедельник услышимся 🙂‍↕️

custom 522006366913983718719custom 52198498184232039337custom 53371737435359342066custom 52197039570388639932

4 Aug 2026, 09:03 UTC257 views47 reactionsread 7 August 2026

На следующей неделе сниппак+трек, а после дроп футболок 🤺

custom 521984981842320393321custom 521970395703886399313custom 522006366913983718710custom 53371737435359342063

4 Aug 2026, 09:00 UTC261 views53 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 522006366913983718727custom 521970395703886399311custom 533717374353593420610custom 52198498184232039335

31 Jul 2026, 13:29 UTC478 views67 reactionsread 7 August 2026

Зимой будет два года как я не курю, иногда хочется просто в дрова уебаться Недавно поспорил, что покурю только, когда у меня будет выступление в Тайланде

custom 521984981842320393326custom 522006366913983718719custom 521970395703886399315custom 53371737435359342067

28 Jul 2026, 16:06 UTC474 views58 reactionsread 7 August 2026
Photo

#0hoes soon 🧑🏼‍🍳 Август сингл + дроп футболок

custom 521970395703886399327custom 522006366913983718716custom 521984981842320393312custom 53371737435359342063

20 Jul 2026, 10:13 UTC618 views63 reactionsread 7 August 2026
Video

На днях выступали, от души, родной Питер! Спасибо близким, спасибо всем, кто нашел время придти послушать 🖤

custom 522006366913983718734custom 521970395703886399314custom 533717374353593420613custom 52198498184232039332

17 Jul 2026, 08:00 UTC602 views40 reactionsread 7 August 2026
Photo

СЕГОДНЯ ЧИТАЕМ РЭПАК❗️ 📍КЛУБ МИРАЖ / 00:00 Исполню старые треки и невыпущенные + запалю новую коллекцию HoodPlaya Билеты на входе, всех жду 💪

custom 522006366913983718717custom 533717374353593420613custom 52198498184232039338custom 52197039570388639932

13 Jul 2026, 09:31 UTC632 views75 reactionsread 7 August 2026
Photo

GAZUEM 🤺

custom 521984981842320393334custom 533717374353593420620custom 522006366913983718719custom 52197039570388639932

6 Jul 2026, 15:49 UTC763 views47 reactionsread 7 August 2026
Forwarded from @Admony

У Кирюхе на Альбике буду😎

custom 522006366913983718727custom 521984981842320393310custom 53371737435359342069custom 52197039570388639931

6 Jul 2026, 15:45 UTC≈2,440 views68 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 522006366913983718736custom 533717374353593420618custom 521984981842320393313custom 52197039570388639931

Showing the 10 most recent of 10 posts we hold for @ashytg. 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 — 48,860 of 1,169,250entries 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.

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.

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

“ASHY 43 💢” (@ashytg), 1,143 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ashytg.

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.