Telegram RegisterThe public register of Telegram
Telegram profile photo for Ашура медляк

Channel

Ашура медляк

@ashura116

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

119subscribers

+12 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1004301811095
TypeChannel
Username@ashura116
CreatedBetween 1 June 2026 and 11 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/ashura116

Growth

10711911312 Aug 2026, 01:02 — 107 subscribers12 Aug 2026, 22:04 — 119 subscribers12 Aug 2026, 01:0212 Aug 2026, 22:04
2 measurements taken within a single day, net +12. 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 105–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:04119+12
12 Aug 2026, 01:02107first reading

Engagement

20 posts held, back to 11 August 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
33.9%
avg views ÷ 119 subscribers
Avg views / post
40.3
16 posts measured
Reaction rate
3.25%
reactions ÷ views · ER floor
Posts in window
20
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. It is computed over the 5 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held20 (11 August 202611 August 2026)
Views total645
Reactions total10
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 01:02 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

10 reactions across 5 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10100.0%

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 5 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 10reactions 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 11 August 2026 to 11 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

11 Aug 2026, 21:20 UTC59 viewsread 12 August 2026
Photo

фаст фк на т7 волгоград обяз подписку @ashura116 @fuckerstorm @softikryt раскид не нужен!! стоп 15 тапов

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

11 Aug 2026, 21:16 UTC19 viewsread 12 August 2026

ща фаст фк ебану

Signed Ashura крутой поц

11 Aug 2026, 20:18 UTC22 views1 reactionsread 12 August 2026

але тапайте

1

Signed Ashura крутой поц

11 Aug 2026, 19:57 UTC23 views1 reactionsread 12 August 2026

если не будете тапать удалю

1

Signed Ashura крутой поц

11 Aug 2026, 19:32 UTC34 views1 reactionsread 12 August 2026

раскид сюда БЕЗ РАСКИДА НЕ ВЫДАМ

1

Signed Ashura крутой поц

11 Aug 2026, 19:31 UTC184 views1 reactionsread 12 August 2026
Photo

Фк на 100 ЗВ сабку на @ashura116 @fuckerstorm @softikryt раскид 10-13 чатов стоп скоро

1

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

11 Aug 2026, 19:29 UTC15 viewsread 12 August 2026
Forwarded from @softikryt

Т7 Волгоград 20 тапов

Signed Softik

11 Aug 2026, 19:28 UTC32 viewsread 12 August 2026
Photo

Photo, posted without a caption

Signed Ashura крутой поц

11 Aug 2026, 19:28 UTC29 viewsread 12 August 2026

щас кину и делаю фк на 100 зв

Signed Ashura крутой поц

Showing the 12 most recent of 20 posts we hold for @ashura116. 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 — 86,813 of 1,481,217entries 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.

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.

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

“Ашура медляк” (@ashura116), 119 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ashura116.

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.