SBOMBA ♥️♥️♥️🕊♥️🕊🔥🔥 ОПРОС ГОСТЕЙ МЕРОПРИЯТИЯ ⚡️- если увидели себя ❤️- если ждете новых мероприятий спасибо всем кто пришел <3
❤22⚡8🍓5

Channel
@saint_events
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
216subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001528655415 |
|---|---|
| Type | Channel |
| Username | @saint_events |
| Description | ОРГАНИЗАЦИЯ КОНЦЕРТОВ И ФЕСТИВАЛЕЙ📸 -отчеты с мероприятий -актуальные новости |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/saint_events |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 10:47 | 216 | no change |
| 7 Aug 2026, 23:01 | 216 | first reading |
15 posts held, back to 10 December 2024 — 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 15 posts for this entry, the most recent from 7 January 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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 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.
185 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 29.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ⚡ | 55 | 29.7% | |
| ❤ | 38 | 20.5% | |
| custom 5336837984467562481 | 37 | 20.0% | |
| custom 5336888025131529697 | 35 | 18.9% | |
| 🍓 | 20 | 10.8% |
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 12 of the 15 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 185reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 10 December 2024 to 7 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
SBOMBA ♥️♥️♥️🕊♥️🕊🔥🔥 ОПРОС ГОСТЕЙ МЕРОПРИЯТИЯ ⚡️- если увидели себя ❤️- если ждете новых мероприятий спасибо всем кто пришел <3
❤22⚡8🍓5
вспомним, как это было! вот и отчетные видос с прошедшего концерта подъехали🔥 как вам?) делитесь впечатлениями в ожидании новых мероприятий<3
🍓8⚡4❤3
SBOMBA ♥️♥️♥️🕊♥️ это был потрясающий сольный концерт Саши! мы повеселились, послушали любимые треки, поймали вайб⭐️ скоро выложим небольшое интервью прямиком с концерта все фото можете посмотреть по ссылкам, может даже себя найдёте)⬇️ 1 ЧАСТЬ 2 ЧАСТЬ
⚡19❤12🍓7
Video message, posted without a caption
custom 53368379844675624817⚡2custom 53368880251315296972❤1
Video message, posted without a caption
custom 53368379844675624818⚡4custom 53368880251315296973
Video message, posted without a caption
custom 53368379844675624816⚡2custom 53368880251315296972
ТАЙМИНГИ ПОМЕНЯЛИСЬ Извиняемся, meet&greet будет сразу после выступления Саши в 21:30!
custom 53368880251315296977
ТАЙМИНГИ⭐ 17:30 - вход meet&greet 18:00 - вход танцпол и вип 22:00 - конец мероприятия до встречи на концерте!
custom 53368880251315296975custom 53368379844675624813⚡2
Закрытие онлайн продаж в 15:00! Последняя повзможность взять билет по доступной цене!
Q&A⭐ Можно ли будет сфоткаться с гостями если случайно увидим их в клубе до начала концерта? если вы вежливо попросите и они не будут заняты/против, то конечно) Будет ли отдельный вход для випов? да, для категории вип отдельный вход без очереди впустят с сопровождением родителей? вы можете прийти с сопровождающим, но у него должен быть билет той же категории, что у вас если потерялся паспорт, можно прийти с свид…
custom 53368379844675624816⚡3custom 53368880251315296973
уже завтра :) https://spb.qtickets.events/139240-solnyy-kontsert-sexbomb
⚡5custom 53368379844675624813custom 53368880251315296972
Photo, posted without a caption
Showing the 12 most recent of 15 posts we hold for @saint_events. 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 — 460,708 of 1,169,250entries 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Saint Events” (@saint_events), 216 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/saint_events.
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.