Channel
@dasha_palovkina
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
117subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001915161028 |
|---|---|
| Type | Channel |
| Username | @dasha_palovkina |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 15 September 2026 |
| On Telegram | t.me/dasha_palovkina |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 16:39 | 117 | -1 |
| 21 Aug 2026, 18:28 | 118 | -1 |
| 15 Aug 2026, 02:46 | 119 | +3 |
| 9 Aug 2026, 05:17 | 116 | no change |
| 6 Aug 2026, 23:18 | 116 | first reading |
6 posts held, back to 19 July 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 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
116 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 25.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5420515131488495294 | 30 | 25.9% | |
| custom 5420133394795224141 | 26 | 22.4% | |
| custom 5420253821383239269 | 26 | 22.4% | |
| custom 5420573392719862417 | 18 | 15.5% | |
| custom 5417914992647232069 | 15 | 12.9% | |
| custom 5418129126831709903 | 1 | 0.862% |
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 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 6 of the 6 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 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 19 July 2026 to 6 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.
Хотела нарисовать облако, а получился растаявший шарик мороженого. Но с такой погодой и облако растает 🍨 #понятныерисования
custom 542051513148849529411custom 54202538213832392697custom 54201333947952241415custom 54205733927198624173custom 54181291268317099031
К сожалению, второго внятного дня на фестивале не случилось, потому что мы сматывали удочки, рвали когти и спешили во всех других формулировках. Но сохранились крохотные скетчи, которые, на мой вкус, содержат в себе ощущение той неторопливости, которая была с нами с самого начала. Маленький формат скетчбука ограничивает в желании запечатлеть все и сразу, так что остается место только для самого важного 🌟 #понятныер…
custom 54205733927198624179custom 54201333947952241414custom 54202538213832392694custom 54205151314884952942
Posted without readable text
custom 542051513148849529413custom 54179149926472320696custom 54201333947952241416custom 54202538213832392693custom 54205733927198624173
Posted without readable text
custom 54179149926472320699custom 54202538213832392694custom 54205151314884952944custom 54205733927198624173custom 54201333947952241412
«точка,запятая.» часть i начинаем знакомить вас с художни_цами, уже ставшей для нас традиционной site-specific выставки, которая расположится недалеко от места действия фестиваля Катя Усова Дарья Паловкина Sofishe Софья Сапожникова Каринэ Андриасян Натали Русинова Шура Чу Л. Горн Жанна Самсонова Дима Бибихин уже в эти выходные ждем вас в подмосковном лесу! вход за донат от 800 р. через бот: ☑️ @nechayno_fest_bot …
custom 54202538213832392693custom 54201333947952241412
"точка, запятая." мы зовем вас в края лесной тиши, чтобы остановить медленное изнашивание повседневности и раскрыть нашу способность к замедлению и соучастию. без ложной осознанности и попыток исправления себя, а через поиск общности с другими, которая сокрыта в содвижении и созамирании, в лесу, в тишине. осталось две недели до нашей встречи, смотрите в карточках, что вас ждет! где и когда: подмосковный лес 1 и 2 …
custom 54201333947952241417custom 54202538213832392695
Showing the 6 most recent of 6 posts we hold for @dasha_palovkina. 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 10 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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Даша!” (@dasha_palovkina), 117 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/dasha_palovkina.
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.