как дела у вас

Channel
ASI ENTERTAINMENT
@ASIoff
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6subscribers
+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 | -1002247356690 |
|---|---|
| Type | Channel |
| Username | @ASIoff |
| Description | Компания по продвижению артистов. Ждем именно тебя!🍓 |
| Created | 12 June 2024 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ASIoff |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:16 | 6 | no change |
| 7 Aug 2026, 16:11 | 6 | first reading |
Engagement
16 posts held, back to 12 June 2024 — 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.
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 September 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 6
- Videos
- 3
- Links
- 3
Lifetime counters from Telegram’s own channel header, read 12 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.
- Video runtime
- 58s
- Average length
- 19s
Measured directly from 3 videos 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.
Reaction mix
51 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 41.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5026216986024084174 | 21 | 41.2% | |
| custom 5028480360774632323 | 11 | 21.6% | |
| custom 5386313177334040817 | 11 | 21.6% | |
| custom 5388863357115713537 | 7 | 13.7% | |
| custom 5386563908934845361 | 1 | 1.96% |
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 6 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 51reactions 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 12 June 2024 to 8 September 2024, 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
Мы закрываемся.
custom 53863131773340408176custom 50262169860240841742
~Юна~🙌
Спасибо вам за 40 подписчиков!🥹🥹
custom 50262169860240841745
~🔤🔤🔤🔤~🙌 t.me/anonaskbot?start=wHsm1LLhoiskKSp ЗАКРЫТ!!!
custom 53863131773340408173
Новая практика! Роль: трейни Песня: I am Псевдоним: Миори Мы будем рады если вы оцените ее навыки🎀
custom 502621698602408417414custom 50284803607746323237custom 53888633571157135376custom 53863131773340408172custom 53865639089348453611
Ребят,хотите практик?
~ 🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤 ~🙌 01. https://t.me/kimyenioff 02. https://t.me/sibiofficialindavix 03. https://t.me/davixenterteinment 04. https://t.me/sara_journ 05. @thegirls_oi 06. https://t.me/safolwen 07. 08. 09. 10. 11. 12. 13. 14. 15.
Я что то не активна…
~ 🔤🔤 🔤 🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤~🙌 ⭐ВП: -Ваш пост на канале держим 30 минут(либо договариваемся). - 0+ -шаблон присылаю в личные сообщения. ⭐СОТРУДНИЧЕСТВО: - пост держим 2-3 часа. -0+ - отписка=разрыв сотрудничества. - после 22:00 репосты не делаем. - не репостим:игры,анон.
С этого момента «DAVIX” и «ASI” сотрудничают!👋 ASI- https://t.me/ASIoff DAVIX- https://t.me/davixenterteinment
Дайте пожалуйста идей как раскрутить компанию😇
Showing the 12 most recent of 16 posts we hold for @ASIoff. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 5
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 5
- vacant every time we have ever looked
@ASIoff named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
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.
“ASI ENTERTAINMENT” (@ASIoff), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ASIoff.
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.