Thanks Valve. MMR reset finally (need some improvements but it’s a beginning)
❤9

Channel
@astinidota
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
498subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001420697822 |
|---|---|
| Type | Channel |
| Username | @astinidota |
| Description | Dota 2 Coach for @PARIVISIONDota2 |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/astinidota |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 04:19 | 498 | no change |
| 7 Aug 2026, 16:56 | 498 | first reading |
15 posts held, back to 3 December 2025 — the 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 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.
| Window | Rolling 30 days · latest post in window 31 July 2026 |
|---|---|
| Posts held | 15 (3 December 2025 – 31 July 2026) |
| Views total | 198 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 04:19 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.
Lifetime counters from Telegram’s own channel header, read 8 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.
Measured directly from 1 video 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.
319 reactions across 15 posts, in 12 distinct kinds. The most used accounts for 59.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 190 | 59.6% | |
| 😁 | 30 | 9.40% | |
| 👍 | 28 | 8.78% | |
| 🔥 | 23 | 7.21% | |
| ❤🔥 | 19 | 5.96% | |
| 🥰 | 13 | 4.08% | |
| 👀 | 4 | 1.25% | |
| 🏆 | 3 | 0.94% | |
| 👎 | 3 | 0.94% | |
| 👻 | 3 | 0.94% | |
| 👏 | 2 | 0.627% | |
| 🤔 | 1 | 0.313% |
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 15 of the 15 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 319reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 3 December 2025 to 31 July 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.
Thanks Valve. MMR reset finally (need some improvements but it’s a beginning)
❤9
Tough one at EWC. For sure that was not the result we were expecting, even with a stack that got together one month before qualifiers. But no regrets. Looking forward, if any team needs a 2nd coach or Analyst I am open for offers for this TI.
❤9😁3🔥1🤔1🥰1
Qualified for EWC. I am glad that at my first qualifier back to competitive I manage to be back to a very important LAN. I almost did not make it. But glad ESL heard our complains and added some integrity check for games. SA region is infested with hacks. At the very least half teams using it. Hope Valve can address it. Because pretending it doesn’t exist so the usage doesn’t grown isn’t working. Soon all rankeds…
👍16❤4👏2🔥2
It is really sad when things dont go as planned. We might be afraid of looking dumb. But I actually think its smart to lower your ego, accept it wasnt wise and move on with lessons learned. https://www.offstage.ru/dota2/news/astini-pro-komandu-s-dm-my-hoteli-sobrat-sostav-sposobnyj-vyigrat-the-international-i-turnir-v-er-riyade
❤21😁3👎2
Yesterday @DMdota17 won PGL Wallachia, standin in for Yandex. Tomorrow we start a new journey together, after being together at PARI (3rd place TI 2025) and Cloud9 (6th place TI 2024) We are looking for a serious organization to represent and build a long term project. Aiming for good placements at EWC/The International. i can be reached at discord : astini
❤16🔥2👎1🥰1
Seems like this was a very expensive voice line.
😁8❤6🏆1
youtu.be/1Hn1gE0tQ0Y New video. Analysis of Team Spirit vs Aurora
❤4👍4
I was planning to add russian subtitles to the "going highground is stupid" video, but I see streamers already understood the rule.
😁12
Ok, soon will be time to coach some 2x TI Winners.
❤34🔥10😁4🏆2
Hi guys. Dropped a new video on my English Channel. Check it out! GOING HIGHGROUND IS STUPID! - THE SECRET OF TIER 1 DOTA https://youtu.be/sorOa6sTd-E
❤9👍2🥰2
Ok I woke up a bit bored cuz group stage kind over for Heroic and decided to make a video to share my macro views on Dota. Why does Nigma throw games? Why Falcons >> OG? I did this video more focused on english speaking community. But I can tell, by watching it you can understand Yatoro tp 6 minutes is game winning. He took Pari mid tower, which gave them not only all early game advantage, but gave them all the fo…
❤12
Temporarily working as an analyst for Heroic in this DreamLeague. Still exploring head coach opportunities for 2026.
❤19👍5🔥4
Showing the 12 most recent of 15 posts we hold for @astinidota. 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.
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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Astini Dota” (@astinidota), 498 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/astinidota.
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.