Channel
@s0ulchemy
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
67subscribers
+8 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004303327472 |
|---|---|
| Type | Channel |
| Username | @s0ulchemy |
| Created | Between 1 June 2026 and 5 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/s0ulchemy |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 91% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 03:15 | 67 | -6 |
| 30 Sept 2026, 09:00 | 73 | +1 |
| 12 Sept 2026, 04:21 | 72 | -3 |
| 3 Sept 2026, 22:36 | 75 | -1 |
| 28 Aug 2026, 06:34 | 76 | +8 |
| 21 Aug 2026, 13:09 | 68 | +8 |
| 13 Aug 2026, 11:37 | 60 | +1 |
| 13 Aug 2026, 08:03 | 59 | first reading |
19 posts held, back to 5 August 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 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 19 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
17 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 47.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5422615838647692970 | 8 | 47.1% | |
| ❤ | 3 | 17.6% | |
| 🔥 | 3 | 17.6% | |
| 🥰 | 3 | 17.6% |
Custom emoji. One 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 count beside it is 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 8 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 17 reactions 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 5 August 2026 to 12 August 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.
список всех результатов кому интересно❤️ хэсу тэйп 7 хэсу лин 7 хэсу тео 7 хэсу янори 5 хэсу тэймор 8 хэсу цундэре 7 хэсу дэмми 9 хэсу элиас 7 хэсу гандон 4 тэйп лин 3 тэйп тео 5 тэйп янори 5 тэйп тэймор 5 тэйп цундэре 10 тэйп дэмми 5 тэйп элиас 5 тэйп гандон 5 лин тео 9 Лин янори 5 лин тэймор 6 лин цундэре 7 Лин дэмми 4 лин элиас 7 лин гандон 5 тео янори 5 тео тэймор 8 тео цундэре 6 тео дэмми 5 т…
custom 54226158386476929701
🔠🔠🔠🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠 @doihaveasoul 🔠🔠🔠 @ankppp 6️⃣/ 16 совпадений🥰 вы сошлись в вопросах 5, 6, 10, 14, 15, 16
custom 54226158386476929701
🔠🔠🔠🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠 ❯❯‶𝐐⃑𝟕⃮𝐀⃪𝐒᷍𝟏⃭𝐑 🔠🔠🔠 @EL11aSs 7️⃣/ 16 совпадений❤️ вы сошлись в вопросах 1, 3, 5, 6, 7, 11, 13
custom 54226158386476929701
🔠🔠🔠🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠 @DE_LUFFINS 🔠🔠🔠 @TQSCG 8️⃣/ 16 совпадений🥰 вы сошлись в вопросах 1, 4, 5, 7, 8, 14, 15, 16
custom 54226158386476929701
🔠🔠🔠🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠 @ffrr1hh 🔠🔠🔠 @BS1K_M 9️⃣/ 16 совпадений🥺 вы сошлись в вопросах 4, 5, 6, 7, 8, 10, 13, 14, 15
custom 54226158386476929701
🔠🔠🔠🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠 @ykklino 🔠🔠🔠 @DSCR1T 1️⃣0️⃣/ 16 совпадений🥰 вы сошлись в вопросах 1, 3, 5, 6, 7, 8, 9, 10, 13, 16
custom 54226158386476929701
🔠🔠🔠🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠 от 𝓛𝓲𝓴𝓼, прекрасного админа @s0ulchemy для участия нужно: 1. быть подписанным на канал 2. быть участником кф 3. поставить точку в комм я пишу каждому в лс вопросы, затем на основе совпадений ответов определяю лучшие шиппы до стопа (стоп после 10 участников, ибо отсматривать все ответы я задолбусь)
custom 54226158386476929701
Sticker, posted without a caption
Video, posted without a caption
❤3🔥3🥰3custom 54226158386476929701
Sticker, posted without a caption
он/а 10 из 10, но заставляет тебя переделывать одно и то же фото 50 раз
Sticker, posted without a caption
Showing the 12 most recent of 19 posts we hold for @s0ulchemy. 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.
Named by 3 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.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“soulchemy” (@s0ulchemy), 67 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/s0ulchemy.
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.