Спасибо всем кто заходил!!❤️❤️❤️ А я снова поучаствовала в мастер-классе у любимой Оксаны и сделала свою мини версию. Похоже?
🔥10custom 53211366663651571047
Signed Татьяна Данкевич

Channel
@dankevicht
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
568subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001885228081 |
|---|---|
| Type | Channel |
| Username | @dankevicht |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/dankevicht |
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 64% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 01:35 | 568 | +1 |
| 2 Sept 2026, 03:48 | 567 | -2 |
| 25 Aug 2026, 08:11 | 569 | -3 |
| 17 Aug 2026, 20:57 | 572 | +4 |
| 11 Aug 2026, 06:15 | 568 | no change |
| 11 Aug 2026, 06:02 | 568 | first reading |
10 posts held, back to 4 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 10 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 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.
93 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 30.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 28 | 30.1% | |
| 🔥 | 21 | 22.6% | |
| custom 5219814084295286024 | 19 | 20.4% | |
| custom 5321136666365157104 | 18 | 19.4% | |
| custom 5249201908391907279 | 4 | 4.30% | |
| custom 5242677827299450340 | 3 | 3.23% |
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 9 of the 10 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 93 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 4 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.
Спасибо всем кто заходил!!❤️❤️❤️ А я снова поучаствовала в мастер-классе у любимой Оксаны и сделала свою мини версию. Похоже?
🔥10custom 53211366663651571047
Signed Татьяна Данкевич
Толик ждет, первые обвесы уже собраны❤️
❤6custom 52426778272994503401
Signed Татьяна Данкевич
Ну вы поняли) приходите сегодня на мастер-класс собирать обвесик Пушкинский сквер, с 12 до 20-21 зависит от погоды Стоимость мк 500 рублей Те кто хочет отдельно бусины тоже приходите!
custom 53211366663651571045❤1
Signed Татьяна Данкевич
Канал Тани Данкевич pinned a photo
Гляньте карамели какие завтра будут
🔥11
Signed Татьяна Данкевич
Пожалуйста загадайте чтобы в субботу на пикнике было без дождя😅
custom 521981408429528602415
Signed Татьяна Данкевич
Video message, posted without a caption
❤2
Signed Татьяна Данкевич
В печке бусины, за окном ливень Сижу вайблю предвкушая скорую осень и делаю кое что новенькое🫢
❤7
Signed Татьяна Данкевич
А это я села лепить снова бусины для будущих мастер-классов, очень счастлива что бусинки быстро разбираются на подвесы :) Кстати если кто-то захочет отдельно купить бусин для своих идей, то тоже приходите 50 рублей штучька
custom 52198140842952860244custom 52426778272994503402
Signed Татьяна Данкевич
Фоторепортаж от Коли с наших посиделок❤️❤️❤️❤️❤️
❤12custom 53211366663651571046custom 52492019083919072794
Signed Татьяна Данкевич
Showing the 10 most recent of 10 posts we hold for @dankevicht. 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.
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“Канал Тани Данкевич” (@dankevicht), 568 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/dankevicht.
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.