❤️ https://x.com/LazAINetwork/status/1963675725052985592
❤9

Channel
@mortalcoin_news
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
733subscribers
-16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002390785118 |
|---|---|
| Type | Channel |
| Username | @mortalcoin_news |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/mortalcoin_news |
Crypto & trading — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 16 Sept 2026, 16:40 | 733 | -2 |
| 9 Sept 2026, 08:59 | 735 | -4 |
| 30 Aug 2026, 04:37 | 739 | -2 |
| 22 Aug 2026, 05:07 | 741 | -3 |
| 14 Aug 2026, 20:08 | 744 | -5 |
| 8 Aug 2026, 02:01 | 749 | no change |
| 7 Aug 2026, 16:26 | 749 | first reading |
20 posts held, back to 20 June 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 20 posts for this entry, the most recent from 5 September 2025. An engagement rate over an empty window would be a number about nothing.
123 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 63.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 78 | 63.4% | |
| 🔥 | 30 | 24.4% | |
| 🏆 | 5 | 4.07% | |
| 👍 | 5 | 4.07% | |
| 🤝 | 3 | 2.44% | |
| 👏 | 1 | 0.813% | |
| 💩 | 1 | 0.813% |
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 18 of the 20 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 123 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 20 June 2025 to 5 September 2025, 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 @mortalcoin_news. 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 20 most recent posts we hold for this entry, published 20 June 2025 to 5 September 2025. 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.
❤️ https://x.com/LazAINetwork/status/1963675725052985592
❤9
Friends, we’ve sent out rewards to all winners of the MortalCoin x Hyperion event leaderboard! Each participant received an additional $3 as we redistributed rewards from the Social campaign. Final rewards (USDT): 0x81C54BF35554213bC86709Ec266E626D40bF8bfD 43 0xD3D820f941899dCB755B2c74bbBc3D7840B65992 35 0x808a8Ca143701f29732839F0Bd18182a2948293E 30 0xA476c76CD375F2199410373d85e36ECb9E834180 23 0x4BC82…
❤5👍1👏1
MortalCoin HyperHack Social Campaign Results: Due to low participant activity, the prize zone was reduced to 5 winners (+1 double prize), and the remaining $44 will be added to the game leaderboard. We’ll contact all the winners on X to get their EVM addresses for prize distribution. Thank you! Winners posts: - https://x.com/akash525111/status/1959222551873196296 (plus a great forum post, contributions from the p…
❤1
The MortalCoin Hyperion event has ended! Key stats: - PvP games played vs Alith-powered AI agent: 1,263 - Users participated: 54 - In-game time: 20+ hours - Game contract transactions on the Hyperion testnet: 23,000+ Huge thank you and appreciation to all the participants. We received tons of valuable feedback and battle reports in the Telegram chat - it will help us improve the game and shape its future. It wa…
❤5
Fighters. You. Are. The. Best.
❤5👍1
Friends, we asked whether you wanted to extend the event, and most of you voted in favor, so the Mortalcoin Hyperion Alpha Testing Tournament will be extended by 24 more hours (until the 25th instead of the 24th). The timer has already been updated. Your opinion is very important to us - thank you!
🔥4
Because of the maintenance that took place, we're considering extending the competition by 24 hours to give everyone a fair chance to take part. Should we extend the deadline? Vote below! 👇
Shares as published. No per-option vote count is published by Telegram, so none is shown.
We were smashing the buttons as fast as we could. The game is back online - please give it a try! 🙂 It should be harder, better, faster and stronger now.
❤2
Dear fighters, It seems there are some bugs, so to fix them and improve the experience, we've paused the game for maintenance. That's why we test on testnet. We expect it to be back in 8–10 hours and will inform you separately once it's live. Thank you!
🤝3❤1
Keep it up, fighters! 🥷 The Alith AI agent is working without rest, battling you. 🙂 It's a great testnet stress test, and your feedback helps make the game better.
❤4
Dear fighters, To keep the competition exciting and ensure a fair comparison of trading skill and luck, we’ve updated the leaderboard calculation rules. Now, only wins from the first 10 fights each day (starting from 00:00 UTC) are counted. The leaderboard has already been recalculated based on this rule, and we’ve also added a 24-hour timer to the interface. This update helps prevent abuse cases (e.g., farming fa…
❤7
Keep it up, fighters! 🥷 You've already played almost 100 games against Alith AI bot. Reloading :)
🔥6💩1
Showing the 12 most recent of 20 posts we hold for @mortalcoin_news. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Because of the maintenance that took place, we're considering extending the competition by 24 hours to give everyone a fair chance to take part. Should we extend the deadline? Vote below! 👇
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 20 June 2025 to 5 September 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
@mortalcoin_news named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“MortalCoin Channel” (@mortalcoin_news), 733 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/mortalcoin_news.
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.