Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐒̶𝐎̴𝐔̴𝐋̷ 𝐒̷𝐓̷𝐄̸𝐀̴𝐋̴𝐄̸𝐑̵𝐒̵

Channel

𝐒̶𝐎̴𝐔̴𝐋̷ 𝐒̷𝐓̷𝐄̸𝐀̴𝐋̴𝐄̸𝐑̵𝐒̵

@soul_stealersss

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

8subscribers

+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-1003373805843
TypeChannel
Username@soul_stealersss
Created19 November 2025 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live19 September 2026
Measurements held2
On Telegramt.me/soul_stealersss

Growth

87 August 2026 — 8 subscribers12 August 2026 — 8 subscribers7 August 202612 August 2026
2 measurements spanning 5 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 7–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 15:188no change
7 Aug 2026, 19:358first reading

Engagement

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

What this channel posts

Photos
4
Links
4

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.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5240403865454523311939.1%
custom 5242397932870711949626.1%
custom 5242498967681384770417.4%
custom 5231390558756289710313.0%
custom 524486654263349938614.35%

Custom emoji. Every row above is a 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 4 of the 7 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 19 November 2025 to 23 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

23 Jun 2026, 07:45 UTC338 views2 reactionsread 12 August 2026
Photo

Ты чувствуешь этот холод? Пора украсть чью-то душу.. 🦇Конференция «Soul stealers» создана для тех, кто не боится заглянуть за край. Для тех, кто ищет истинные мотивы человеческой души. 🍷Это не просто конференция. Это ритуал погружения в темную философию и глубинные смыслы. Здесь не будет комфорта. Здесь будет только истина… Также активно ищем админов. Channel | Rules | Chat

custom 52423979328707119491custom 52424989676813847701

3 Dec 2025, 10:30 UTC233 views10 reactionsread 12 August 2026

Ещё раз хочу выразить огромную благодарность студии «кальян». Давно слежу за его работами, впервые решил заказать оформление для своей конференции и не пожалел! Желаю дальнейшего продвижения.😊

custom 52404038654545233115custom 52423979328707119493custom 52424989676813847702

3 Dec 2025, 10:30 UTC144 viewsread 12 August 2026
Forwarded from @studio_kaelPhoto

🔤esign for t.me/soul_stealersss 💬 contact me 🤩 review Happy New Year, have a great winter! With love, Hookah

3 Dec 2025, 10:21 UTC602 views6 reactionsread 12 August 2026
Photo

‼️Похитители душ открывают набор в чат. Для вступления вам потребуется: 🩸Подписаться на наш канал. 🩸Прочитать правила. 🩸Подать заявку в чат.

custom 52404038654545233113custom 52313905587562897101custom 52423979328707119491custom 52448665426334993861

3 Dec 2025, 10:06 UTC192 views5 reactionsread 12 August 2026
Photo

🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🪚🪚🪚🪚🪚🪚🪚🪚🪚 rules administration chat boots archive 🌟🌟🌟🌟🌟🌟🌟🌟🌟 ❤️As of December 3, 2025, the name "Soul stealers" is exclusively owned by the owner of this conference. If I see its use, I have the right to ask you to change or remove the plagiarism, and if you do not hear me, I will take action.

custom 52313905587562897102custom 52404038654545233111custom 52423979328707119491custom 52424989676813847701

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

Forward network

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.

Mentions

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.

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

“𝐒̶𝐎̴𝐔̴𝐋̷ 𝐒̷𝐓̷𝐄̸𝐀̴𝐋̴𝐄̸𝐑̵𝐒̵” (@soul_stealersss), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/soul_stealersss.

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.