Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝖲𝗈𝗎𝗅𝗠𝗲𝘀𝘀 : 📬邮件

Channel

𝖲𝗈𝗎𝗅𝗠𝗲𝘀𝘀 : 📬邮件

@SoulMessText

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

219subscribers

+5 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003780775154
TypeChannel
Username@SoulMessText
CreatedBetween 1 February 2026 and 1 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 16 September 2026
On Telegramt.me/SoulMessText

Topic

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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.

Growth

2142202179 August 2026 — 214 subscribers9 August 2026 — 214 subscribers17 August 2026 — 217 subscribers24 August 2026 — 218 subscribers31 August 2026 — 220 subscribers8 September 2026 — 219 subscribers2199 August 20268 September 2026
6 measurements spanning 30 days, net +5. 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 213–221 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 12:19219-1
31 Aug 2026, 05:13220+2
24 Aug 2026, 03:27218+1
17 Aug 2026, 10:06217+3
9 Aug 2026, 11:00214no change
9 Aug 2026, 10:52214first reading

Engagement

19 posts held, back to 1 July 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

121 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 50.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54067591930529951736150.4%
custom 54066312760420027966049.6%

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 7 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 121 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 1 July 2026 to 8 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.

Telegram Stars

Stars received
45
across the posts below
Posts paid on
2
of 19 we hold a reading for · 11%
Most on one post
30
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @SoulMessText. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 19 most recent posts we hold for this entry, published 1 July 2026 to 8 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

8 Aug 2026, 15:37 UTC88 views16 reactionsread 9 August 2026

я хочу извиниться перед всеми, кто стал свидетелем этой ситуации (т.е. разбора на меня) и кого прямо или косвенно затронули мои поступки. я признаю свою вину и искренне раскаиваюсь в том, что сделала, понимаю свои ошибки и уже сделала из них выводы. вы могли это заметить по тому, что я долго отсутствовала и у меня было время подумать об этом. со своей стороны я лично закрыла недопонимания и разногласия с людьми, кото…

custom 54066312760420027968custom 54067591930529951738

20 Jul 2026, 10:06 UTC306 views19 reactionsread 9 August 2026
Photo

ᅠ Tɑllυᩛׄ ჩelp : 空🐬 𝗗𝗘𝗦𝗜𝗚𝗡 𝖢𝖮𝖭𝖳𝖤𝖲𝖳 𝗛𝗔𝗣𝗣𝗬 9k - - Сgелɑú gля нɑс эру! Всем привет, в честь 9К подписчиков мы рады объявить о начале творческого конкурса на лучшее оформление для нашего канала! Это отличная возможность проявить свои творческие способности, а также побороться за ценный приз. С нетерпением ждём ваши работы и желаем каждому участнику вдохновения и удачи! 💫' Для учɑстuя неоδхоguмо O1. Подписка на…

custom 540675919305299517310custom 54066312760420027969

20 Jul 2026, 10:06 UTC242 viewsread 9 August 2026

🗯️邮件 𝗡𝗲𝘄𝖮𝗋𝖽𝖾𝗋﹙ fσr @tallyhlp ﹚

16 Jul 2026, 22:56 UTC330 views19 reactionsread 9 August 2026
Photo

ᅠ 𝓕𝖺𝗂𝗋𝗒 「 정원 𝟶𝟷. 𝖧𝖾𝗅𝗉 」— 𝖠 𝗉𝗋𝗂𝗇c⃨e⃨s⃨s⃨ ჩ𝑎𝗌𝗁𝗍𝑎𝗀𝗌,⿻ 𝗶𝗻𝗳𝗼 / 🌹동화 𝗍𝗁𝗂𝗌 𝗍𝑎𝑙𝑒! 𝙰𝗻𝗼𝗻 @ ᨢִom : 월𐚁 𝗮𝗹𝗹𝗼𝘄 αdmins

custom 540663127604200279610custom 54067591930529951739

16 Jul 2026, 22:55 UTC301 viewsread 9 August 2026

🗯️邮件 𝗡𝗲𝘄𝖮𝗋𝖽𝖾𝗋﹙ fσr @FAIRYHLP ﹚

6 Jul 2026, 18:08 UTC482 views12 reactionsread 9 August 2026
Photo

ᅠ 𝑀ıd𝗡𝗶𝗴𝗵𝘁 𝖧𝖾𝗅𝗉 : 🤩타일 𝖲𝖴𝖬𝖬𝖤𝖱 2O̤ TꮛɑmWork < ❨ se⍺rch բor 𝗮𝗱𝗺𝗶𝗻𝘀 ❩ Для mого чmоδы сmаmь аgмuном O1. ♫ Уметь искать качественный материал O2. ♫ Быть активным, выполнять норму O3. ♫ С ответственностью относится к материалу. Не брать материал с других хелпов, отмечать источники + Н౿ поgавайmе анкеmყ, еслu вы O1. 𖥔 Вы участвовали в больших и серьезных конфликтах. O2. 𖥔 Вы не умеете работать в команде. O3. 𖥔 Ваш уровень …

custom 54067591930529951737custom 54066312760420027965

6 Jul 2026, 18:07 UTC358 viewsread 9 August 2026

🗯️邮件 𝗡𝗲𝘄𝖮𝗋𝖽𝖾𝗋﹙ fσr @m1dhelpp ﹚

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

Mentions

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.

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

“𝖲𝗈𝗎𝗅𝗠𝗲𝘀𝘀 : 📬邮件” (@SoulMessText), 219 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/SoulMessText.

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.