#𝐕𝐈𝐃𝐄𝐎✨ Cr: Vishn Тт: mortels
custom 53505125547476533805custom 54111254396262400223custom 52830572415056944962custom 53503368089808686302custom 53503388190255667312custom 53503828768000848882custom 53505085861978735212custom 53506596788523784072

Channel
@mortellss
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
118subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002371243217 |
|---|---|
| Type | Channel |
| Username | @mortellss |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/mortellss |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 03:28 | 118 | -5 |
| 9 Aug 2026, 03:03 | 123 | no change |
| 7 Aug 2026, 17:25 | 123 | +1 |
| 7 Aug 2026, 02:45 | 122 | first reading |
17 posts held, back to 5 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 13 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 17 (5 July 2026 – 6 August 2026) |
| Views total | 2,691 |
| Reactions total | 283 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 03:03 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 13 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.
339 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 15.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5350512554747653380 | 53 | 15.6% | |
| custom 5350783167752074667 | 51 | 15.0% | |
| custom 5350508586197873521 | 46 | 13.6% | |
| custom 5350336808980868630 | 45 | 13.3% | |
| custom 5411125439626240022 | 44 | 13.0% | |
| custom 5350338819025566731 | 26 | 7.67% | |
| custom 5350382876800084888 | 26 | 7.67% | |
| custom 5350323215409377064 | 22 | 6.49% | |
| custom 5350659678852378407 | 11 | 3.24% | |
| custom 5283057241505694496 | 9 | 2.65% | |
| custom 5352873953536801333 | 6 | 1.77% |
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 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 16 of the 17 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 339reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 5 July 2026 to 6 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mortellss. 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 17 most recent posts we hold for this entry, published 5 July 2026 to 6 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.
#𝐕𝐈𝐃𝐄𝐎✨ Cr: Vishn Тт: mortels
custom 53505125547476533805custom 54111254396262400223custom 52830572415056944962custom 53503368089808686302custom 53503388190255667312custom 53503828768000848882custom 53505085861978735212custom 53506596788523784072
#𝐂𝐎𝐋𝐋𝐀𝐁𝐎𝐑𝐀𝐓𝐈𝐎𝐍✨ 𝐂𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧 𝐛𝐞𝐭𝐰𝐞𝐞𝐧 𝐌𝐎𝐑𝐓𝐄𝐋𝐒 𝐚𝐧𝐝 𝘼𝙢𝙗𝙚𝙧 𝙁𝙡𝙖𝙢𝙚 Cr: Luna × Miko Tт: Mortels × Amber Flame
custom 53507831677520746679custom 53506596788523784074custom 53503368089808686303custom 52830572415056944962custom 53503232154093770642custom 53505085861978735212custom 53505125547476533802custom 54111254396262400222
#𝐕𝐈𝐃𝐄𝐎✨ Cr: Vishn Тт: mortels
custom 535078316775207466711custom 53503388190255667317custom 53505125547476533807custom 53503828768000848882custom 53505085861978735212custom 53528739535368013332custom 54111254396262400222
#𝐕𝐈𝐃𝐄𝐎✨ Cr: Vishn Тт: mortels
custom 53503368089808686306custom 53503232154093770644custom 53503388190255667313custom 53503828768000848883custom 53505125547476533803custom 53506596788523784073custom 53507831677520746672
#𝐕𝐈𝐃𝐄𝐎✨ Cr: Vishn & Joker Тт: mortels
custom 53503388190255667318custom 54111254396262400227custom 53505125547476533806custom 52830572415056944965custom 53503368089808686302custom 53505085861978735212custom 53506596788523784072custom 53528739535368013332
#𝐂𝐎𝐋𝐋𝐀𝐁𝐎𝐑𝐀𝐓𝐈𝐎𝐍✨ 𝐂𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧 𝐛𝐞𝐭𝐰𝐞𝐞𝐧 𝐌𝐎𝐑𝐓𝐄𝐋𝐒 𝐚𝐧𝐝 𝐋𝐄𝐙𝐁𝐔𝐇𝐈 Cr: Luna & Kiesao Tт: Mortels × Lezbuhi
custom 53505085861978735217custom 53503368089808686304custom 53505125547476533803custom 54111254396262400222
🤩🤩 рады объявить, что с 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 «𝐌𝐎𝐑𝐓𝐄𝐋𝐒» заключает союз с конференцией «𝘼𝙢𝙗𝙚𝙧 𝙁𝙡𝙖𝙢𝙚» 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 Мы убеждены, что данное партнерство заложит надежный фундамент для роста наших объединений и воплощения общих замыслов. 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 Нам бы хотелось, чтобы общее дело наполнило нас радостными мгновениями, интересными собеседниками и незабываемыми событиями. 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 Так же хотели бы поблагодарить конференцию …
custom 53507831677520746675custom 53503368089808686303custom 53505085861978735213custom 53505125547476533802custom 54111254396262400222
#𝐂𝐎𝐋𝐋𝐀𝐁𝐎𝐑𝐀𝐓𝐈𝐎𝐍✨ 𝐂𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧 𝐛𝐞𝐭𝐰𝐞𝐞𝐧 𝐌𝐎𝐑𝐓𝐄𝐋𝐒 𝐚𝐧𝐝 𝑩𝑼𝒁𝒁𝑭𝑬𝑬𝑫 Cr: Luna & Tay Tт: Mortels × Buzzfeed
custom 53505125547476533807custom 53505085861978735215custom 53507831677520746675custom 54111254396262400222
#𝐕𝐈𝐃𝐄𝐎 Cr: Luna Тт: mortels
custom 53503368089808686308custom 53503828768000848885custom 54111254396262400225custom 53503232154093770642custom 53505085861978735212custom 53505125547476533802
#𝐕𝐈𝐃𝐄𝐎 Cr: Luna Тт: mortels
custom 53505125547476533806custom 54111254396262400226custom 53503232154093770642custom 53503828768000848882custom 53505085861978735212custom 53507831677520746672
#𝐕𝐈𝐃𝐄𝐎✨ Cr: Dein Тт: mortels
custom 53503828768000848884custom 53507831677520746674custom 53503368089808686302custom 53505085861978735212custom 53503232154093770641custom 53505125547476533801custom 54111254396262400221
🤩🤩 с гордостью сообщаем, что с 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 «𝐌̷𝐎̇𝐑̸𝐓̷𝐄̅𝐋̇𝐒̸» и конференция «𝑩𝑼𝒁𝒁𝑭𝑬𝑬𝑫» официально скрепляют союз. 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 Это партнерство станет прочным трамплином для наших амбиций, точкой опоры для смелых решений. Пусть наше сотрудничество подарит нам вдохновляющие открытия, яркие эмоции и возможность создать нечто большее. 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 Отдельное спасибо конференции «𝑩𝑼𝒁𝒁𝑭𝑬𝑬𝑫» за оказанное доверие и готовность разде…
custom 53507831677520746674custom 54111254396262400224custom 53503828768000848882custom 53503232154093770641custom 53503368089808686301custom 53505085861978735211
Showing the 12 most recent of 17 posts we hold for @mortellss. 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 — 271,671 of 1,336,469entries 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 4 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐌̷𝐎̇𝐑̸𝐓̷𝐄̅𝐋̇𝐒̸” (@mortellss), 118 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/mortellss.
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.