Telegram RegisterThe public register of Telegram

Channel

дᴀɯуᴧя/ᴀᴧиᴄᴋᴀ ᴋᴏʍʍᴇнᴛиᴩуюᴛ🫶🏻

@dashulya_aliska

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

28subscribers

+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-1002715501687
TypeChannel
Username@dashulya_aliska
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/dashulya_aliska

Growth

287 August 2026 — 28 subscribers11 August 2026 — 28 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 27–29 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 06:3128no change
7 Aug 2026, 18:1228first reading

Engagement

11 posts held, back to 5 October 2025the 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 11 posts for this entry, the most recent from 1 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
339
Videos
13
Links
8

Lifetime counters from Telegram’s own channel header, read 11 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
33s
Average length
17s

Measured directly from 2 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

20 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 35.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5429212938479109724735.0%
❤‍🔥630.0%
custom 5188169345078939401420.0%
315.0%

Custom emoji. 2 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 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 11 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 20reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 5 October 2025 to 1 January 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.

Recent posts

1 Jan 2026, 18:41 UTC43 viewsread 11 August 2026

проголосуйте за два пожалуйста

4 Dec 2025, 15:30 UTC47 viewsread 11 August 2026
Forwarded from @photoprosportPhoto

😜🙈🤗😂😂😂

30 Oct 2025, 07:53 UTC121 views0 reactionsread 11 August 2026
Photo

Сегодня 30 октября, отмечается День тренера! ❤️ Поздравляем всех тренеров, спасибо им за такой вклад в гимнастику. Желаем улыбок, спокойствия, и всего самого лучшего! 💞

26 Oct 2025, 14:50 UTC96 views3 reactionsread 11 August 2026
Photo

Эва,красотка! ♥️ #photo #ЭваТандалова 📸: Федерация гимнастики и ОФК Эвы

❤‍🔥3

25 Oct 2025, 09:41 UTC77 views5 reactionsread 11 August 2026
Photo

эмоции Настюши 🪦 ➿➿➿➿➿➿➿ #photo #НастяВласенко 📸:@singledphoto

custom 51881693450789394013custom 54292129384791097242

25 Oct 2025, 09:34 UTC67 views3 reactionsread 11 August 2026

Добрый день, извините за наше долгое отсутствие 💔 давайте много реакций, и актива, все встанет на свои места ❤️

❤‍🔥1custom 51881693450789394011custom 54292129384791097241

16 Oct 2025, 21:05 UTC86 views2 reactionsread 11 August 2026
Video

Кристина,с днём рождения!🥳Наш лучик солнца🫶🏻🔅 реакции пожалуйста🫶🏻 #Edit #КристинаКуракова //-@dashulya_aliska

custom 54292129384791097242

15 Oct 2025, 19:23 UTC98 views7 reactionsread 11 August 2026
Video

Алиска😍 реакции пожалуйста🫶🏻 #Edit #АлисаМедведева //-@dashulya_aliska

3❤‍🔥2custom 54292129384791097242

5 Oct 2025, 07:04 UTC102 viewsread 11 August 2026
Photo

Передающиеся купальники💕 //@dashulya_aliska

Showing the 11 most recent of 11 posts we hold for @dashulya_aliska. 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

Citation-graph rank — 979,805 of 1,478,351entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“дᴀɯуᴧя/ᴀᴧиᴄᴋᴀ ᴋᴏʍʍᴇнᴛиᴩуюᴛ🫶🏻” (@dashulya_aliska), 28 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/dashulya_aliska.

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.