Channel
@AwesomSO2
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
189subscribers
-11 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002205056950 |
|---|---|
| Type | Channel |
| Username | @AwesomSO2 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/AwesomSO2 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 22:40 | 189 | -5 |
| 28 Aug 2026, 14:28 | 194 | -1 |
| 22 Aug 2026, 14:12 | 195 | -2 |
| 15 Aug 2026, 16:08 | 197 | -2 |
| 8 Aug 2026, 16:34 | 199 | -1 |
| 8 Aug 2026, 11:31 | 200 | no change |
| 8 Aug 2026, 06:00 | 200 | first reading |
16 posts held, back to 2 August 2026 — 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 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 16 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
155 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 29.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5235770008059020151 | 46 | 29.7% | |
| 👍 | 23 | 14.8% | |
| 😢 | 22 | 14.2% | |
| custom 5370815732739219327 | 21 | 13.5% | |
| 🏆 | 21 | 13.5% | |
| custom 5999168292797813666 | 18 | 11.6% | |
| custom 5998988724510133961 | 4 | 2.58% |
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 16 of the 16 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 155 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 2 August 2026 to 8 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.
Официально хотим объявить наш новый ростер, который будет играть на предстоящих турнирах: — Awesom — trkk — Eternal — Huges — D1serk Team Staff: • Роман «Literally» — Owner • Антон «Reborn» — СЕО • Артем «Hoffman» — Head Мanager • Иван «Lireklly» — SMM Давайте поддержим ребят в коментариях!
custom 52357700080590201511custom 53708157327392193271custom 59991682927978136661
с др пухлого
custom 52357700080590201512custom 53708157327392193271custom 59991682927978136661
Video message, posted without a caption
custom 52357700080590201512custom 59991682927978136662👍1
Eternal prime 😨
custom 52357700080590201516custom 53708157327392193272custom 59991682927978136662
с вторым местом поздравляют 🔥
🏆6custom 53708157327392193275custom 52357700080590201514
Video message, posted without a caption
custom 52357700080590201516custom 53708157327392193272custom 59991682927978136662👍1
найден софтер, срочно баним!!!
👍7😢3custom 53708157327392193273
Всем спасибо за поддержку ребят, каждого ценю! 💙
custom 52357700080590201518🏆4custom 59991682927978136663custom 59989887245101339611
Пост про финал: Hanami 🗺️ – сыграли хорошо с условием того что давно не играли мапу, 7:5 атака и 13:10 закончили легко и вышли на 1:0. Sandstone 🗺️ – плохо за кт, много своего залили 5:7 а за тешку вообще потерялись вот и 13:9, 1-1. Dune 🗺️ – за кт 6:0 идем, все клатчи берем потом отдаем на 7:5 но за тешку собрались и закончили эту карту 13:8 отдав всего 1 раунд за тешку, 2-1. Rust 🗺️ – тут и начался самый пиздец…
custom 52357700080590201516🏆3😢3
проебали
😢4👍2custom 52357700080590201512
2-1
👍3😢3custom 52357700080590201513🏆1
переигровка раста, справедливо.
👍3custom 52357700080590201513custom 59991682927978136662😢1custom 53708157327392193271
Showing the 12 most recent of 16 posts we hold for @AwesomSO2. 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.
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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Awesom?🪽” (@AwesomSO2), 189 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/AwesomSO2.
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.