Telegram RegisterThe public register of Telegram

Channel

Сашко Бубляж

@xatasashka

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

54subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002094799620
TypeChannel
Username@xatasashka
Descriptionщо таке той ваш фандаб… Звʼязок зі мною: @hordisl
Created11 May 2024measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/xatasashka

Growth

546 August 2026 — 54 subscribers10 August 2026 — 54 subscribers6 August 202610 August 2026
2 measurements spanning 3 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 53–55 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 08:3154no change
6 Aug 2026, 21:1654first reading

Engagement

19 posts held, back to 11 May 2024the 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 19 posts for this entry, the most recent from 8 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
5
Videos
2
Links
10

Lifetime counters from Telegram’s own channel header, read 10 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
2m 53s
Average length
1m 27s

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

128 reactions across 17 posts, in 11 distinct kinds. The most used accounts for 71.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
9171.1%
🔥1310.2%
👍64.69%
🍓43.13%
🎉32.34%
🙈32.34%
🥰32.34%
💋21.56%
🍌10.781%
👏10.781%
🤣10.781%

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

Measured over the 19 most recent posts we hold, published 11 May 2024 to 8 June 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

8 Jun 2026, 00:09 UTC128 views5 reactionsread 10 August 2026

щось висираю🛁 я не мертвий, люди, скоро почну поповнювати канал

5

9 Feb 2026, 01:25 UTC376 views3 reactionsread 10 August 2026

Зробили дубляж сінематика овервотч "Shooting Star", той самий про Діву 🐰 Якщо у моєму каналі є шанувальники цієї гри, то біжіть гляньте тут → futashine 🐼 (не шанувальники теж, бо дубляж крутецький)👀

🔥3

3 Jan 2026, 12:24 UTC472 views10 reactionsread 10 August 2026
Photo

Друзі, усіх вітаю з новим роком! 🎄✨ Бажаю міцного здоров’я, радості в кожному дні, здійснення мрій і тепла від рідних людей. Нехай новий рік принесе мир, удачу та багато щасливих моментів! 🫂

9🍓1

22 Dec 2025, 06:44 UTC354 views6 reactionsread 10 August 2026
Forwarded from @futashine_uaPhoto

Вітаємо з Днем народження, Hordi❤️ Бажаємо тобі сил і впевненості у власних рішеннях, стабільності в справах і внутрішнього спокою🦋 Нехай поруч будуть люди, з якими легко, а можливості з’являються вчасно🏅 Хай кожен новий день приносить щось корисне, добре й варте зусиль🍀 Нехай у житті буде більше ролей, у яких ти відчуваєш себе на своєму місці, більше проєктів, що надихають, і людей, з якими легко працювати🎂

4🔥2

20 Dec 2025, 23:18 UTC291 views7 reactionsread 10 August 2026
Forwarded from @my_saralPhoto

🐣☀️З ДНЕМ НАРОДЖЕННЯ!!! 🍾🎉 Сьогодні день народження у найяскравішої, найкрутішої й найближчої для мене людини!😎👑🥳🥳🥳🥳 Ти - моє кохання, найважливіша людина, найкращий друг, натхнення, моє щастя та майбутнє!💗😘💞 Я щиро бажаю тобі залишатись таким же добрим, смішним, чуйним, цілеспрямованим і сильним!💪😼 Також бажаю міцного здоров'я, якомога більше радощів у житті, щастя, успіху і втілення всіх-всіх бажань! 💗✨💗✨💗✨ Я д

3🎉3🍌1

20 Dec 2025, 23:18 UTC207 views3 reactionsread 10 August 2026

Дякую тобі, кохана! Ти найкраща!🫂💗💓💞🩷💕💘

3

1 Oct 2025, 13:19 UTC419 views11 reactionsread 10 August 2026
Forwarded from @ssternenko

Сьогодні День захисників та захисниць. Дякую кожному та кожній, хто боронить Україну, захищає Європу та НАТО. Вітайте військо донатом на русоріз!

11

23 Aug 2025, 00:10 UTC584 views7 reactionsread 10 August 2026

Оцьо дроп! 😋 Цікаво, хто з вас теж грає в овервотч? Відпишіть у коментарях! 🫶✨

🍓32🔥2

23 Aug 2025, 00:10 UTC525 views5 reactionsread 10 August 2026
Forwarded from @futashine_ua

Овервотч / Overwatch Історія походження: Раматтра 🐼@FutaShine_ua🐼 https://youtu.be/4fSHgrOBNJM https://youtu.be/4fSHgrOBNJM https://youtu.be/4fSHgrOBNJM Озвучили: Раматтра - Genk1to 📼Режисер: Hordi 🔊Звукорежисер: Alchemist 🖼Локалізація: LinLin 👤Менеджер проєкту: Hordi, Noijii 📚Переклад: Hordi ✅Контроль якості: Alchemist, Hordi, Noijii 💰Підтримати нас: 🏦МоноБанка 🎨 Patreon Та не забувайте підписуватися на інші

🔥32

19 Aug 2025, 17:05 UTC480 views8 reactionsread 10 August 2026
Video

"Він такий відповідальний, у вільний час розвивається та навчається"🗣🔥 Що я роблю у вільний час насправді:

4🙈3👏1

6 Jul 2025, 20:25 UTC526 views8 reactionsread 10 August 2026

Ой ой ой, го дивитись🤩

8

Showing the 12 most recent of 19 posts we hold for @xatasashka. 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 — 484,668 of 1,350,102entries 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

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.

Mentions

Named by 14 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.

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.

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

“Сашко Бубляж” (@xatasashka), 54 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/xatasashka.

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.