Channel
@aliska_veda
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003840538358 |
|---|---|
| Type | Channel |
| Username | @aliska_veda |
| Created | Between 1 February 2026 and 21 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/aliska_veda |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 02:01 | 14 | no change |
| 9 Aug 2026, 06:45 | 14 | first reading |
20 posts held, back to 21 February 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 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 20 posts for this entry, the most recent from 16 March 2026. An engagement rate over an empty window would be a number about nothing.
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.
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.
67 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 64.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 43 | 64.2% | |
| 🔥 | 16 | 23.9% | |
| 👍 | 5 | 7.46% | |
| 🕊 | 2 | 2.99% | |
| 🤯 | 1 | 1.49% |
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 17 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 67reactions 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 21 February 2026 to 16 March 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.
Выбери поэта и приготовься к эпическому сражению. Кто победит: решает зритель. ПОЛЕ БРАНИ | краснодарский поэтический слэм ⚙ ТЕХНИЧЕСКИЕ ХАРАКТЕРИСТИКИ: Релиз: 22.03.2026 Разработчики: ПТИЦЫ | поэтический клуб Платформа: живая сцена (без эмуляции) Жанр: поэтический слэм Версия: 1.0 (полноценный релиз) Режим игры: парные выступления, битвы поэтов Движок: голос + эмоции Системные требования: открытый слух, готовност…
Сделала песню на старые стихи. Добавила припев. Получилось весьма интересно🔥🔥🔥
❤3
Channel photo updated
Когда у меня поедет крыша, я об этом никому не скажу, но... знаки однозначно будут 👌🥴
❤5🤯1
А ещё! Сегодня принимаю участие в слэме 😎 Удачи мне и всем участникам 🍀
❤7
А ещё сегодня день котов и кошек 🐈
❤3
Всех всех — с Весной 🍀
❤4
Впервые! Битва прозаиков: Слово — не воробей, а призовой фонд 🎤💰 Привыкли, что на сцене звучат только стихи? А что, если проза обретет голос? В это воскресенье состоится событие, которого еще не было в нашем городе — СЛЭМ ПРОЗАИКОВ Краснодар Кто эти смельчаки, рискнувшие выйти к микрофону без рифмы, полагаясь только на силу слова, сюжета и харизмы? Кто из них сможет удержать внимание зала и сорвать куш? Вот же они…
❤3
Приходи меня поддержать 😉 Жду 🫶
🔥2
Всем доброго и прекрасного дня желаю от души. ☕ Люблю каждого в моём тг канале ❤️ Обняла 🫶 А жизнь, она действительно - такова 😁
🔥5
Это что-то невероятное!! Ауууф!!! 🐺
ГОЛОС, ТЕКСТ, СЛЭМ! ХВАТИТ ПИСАТЬ В СТОЛ — ВЫХОДИ НА СЦЕНУ! Друзья, мы запускаем уникальную литературную битву СЛЭМ ПРОЗАИКОВ Краснодар. Это не тихие чтения для своих. Это конкурс, где твой текст звучит, а зал решает, кто круче. Суть: Мы ищем 16 смелых авторов, готовых не только написать, но и прожить свой текст на сцене. У тебя есть 7 минут, чтобы прочитать малую прозу или отрывок. Зрители ставят две оценки: текс…
🔥2
Showing the 12 most recent of 20 posts we hold for @aliska_veda. 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 — 1,287,879 of 1,480,944entries 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.
Named by 1 registered channel — 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.
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.
“Алиса вещает и вдохновляет ❤️” (@aliska_veda), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/aliska_veda.
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.