Channel
@SLselia
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
12subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003624767880 |
|---|---|
| Type | Channel |
| Username | @SLselia |
| Description | 𝗌𝗍𝖺𝗋𝗍 : 2.02.26 ¡ → 𝗈𝗐𝗇𝖾𝗋 : @tropik01 ‹‹ 𝗂nfo 𝖼𝗁𝖺𝗇𝗇𝖾𝗅 : @SLseli_info |
| Created | Between 1 December 2025 and 13 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/SLselia |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:31 | 12 | no change |
| 12 Aug 2026, 23:17 | 12 | first reading |
18 posts held, back to 13 March 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 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 18 posts for this entry, the most recent from 5 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
35 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 20 | 57.1% | |
| 🍓 | 5 | 14.3% | |
| 👀 | 2 | 5.71% | |
| 🔥 | 2 | 5.71% | |
| 🤯 | 2 | 5.71% | |
| 🥰 | 2 | 5.71% | |
| 🆒 | 1 | 2.86% | |
| 💋 | 1 | 2.86% |
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 15 of the 18 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 35reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 13 March 2026 to 5 April 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.
Здравствуйте, думаю это уже было понятно. Мы закрываемся, и всех благодарю за то что поддерживали мой канал все это время !! У меня сейчас большие семейные проблемы и за каналом уследить я не могу. И я очень благодарна за все 30 пдп. Было приятно заниматься каналом и т.д. Со всеми союзниками разрыв.
🤯2
Sticker, posted without a caption
❤1
Sticker, posted without a caption
❤1
Sticker, posted without a caption
❤1
◜𝐍𝖾.𝗐 𝗉𝗈𝗌𝗍 . . ^᪲᪲᪲ . . #𝑺𝑳 𐙚 . . T𝗲xᴛ : йоо как прикольна 𐀔. ›› 𝗍𝗂𝘁𝗹𝖾 : Туалетный мальчик Ханако #тмх ⤻ 𝖺𝗱.𝗺𝗂𝗇 : #𝑆𝑒𝑙𝑖𝑎 ✦ » #баннер #практика « ✦ —
🍓2🔥1🥰1
После концерта, уставшая, но довольная, я зашла в любимое кафе. Привычная атмосфера джаза и кофе успокаивала. Собираясь к столику у окна, я заметила незнакомца(ку), погруженного(ую) в чтение. Его(ё) сосредоточенность заинтриговала. Подойдя, я предложила выпить кофе. Он(а) поднял(а) голову, и его(ё) глубокие глаза встретились с моими. С легкой улыбкой он(а) согласился(ась). За капучино мы начали разговор. Сначала о …
❤3
Channel name was changed to «𝆭 𝆹𝅥𝗦𝗲𝗹𝗶 𔔁݂` .»
Разрыв с такими проектами как https://t.me/ZazengProgect Причина: закрытие😔 https://t.me/Fox_lles Тоже закрытие 😔 https://t.me/yajeukidkm Тоже закрытие 😔 #разрыв
❤2
Sticker, posted without a caption
❤1
Выходим из реста!! (надеюсь меня союзники не ненавидят)
❤2
Channel name was changed to «Рест 𝆭 𝆹𝅥𝗦𝗲𝗹𝗶 𔔁݂` .»
Извините в тот раз не сказала полностью причину реста. Рест будет до 24 марта до этого у меня вообще не будет интернета и связи из-за поездки репостов и постов тоже не будет. После реста доделаю итоги интерактива🥰 (возможно пиздеж) #репост #важно
❤3💋1🥰1
Showing the 12 most recent of 18 posts we hold for @SLselia. 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 — 833,585 of 1,480,688entries 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.
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 2 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“𝆭 𝆹𝅥𝗦𝗲𝗹𝗶 𔔁݂` .” (@SLselia), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SLselia.
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.