Telegram RegisterThe public register of Telegram
Telegram profile photo for Mortal Kombat | confession & daily!

Channel

Mortal Kombat | confession & daily!

@mortalkombatcfdaily

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

818subscribers

+41 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-1002495790883
TypeChannel
Username@mortalkombatcfdaily
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/mortalkombatcfdaily

Topic

Gaming — 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 100% 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

777818797.57 August 2026 — 777 subscribers8 August 2026 — 777 subscribers16 August 2026 — 780 subscribers23 August 2026 — 788 subscribers29 August 2026 — 790 subscribers8 September 2026 — 805 subscribers16 September 2026 — 818 subscribers7 August 202616 September 2026
7 measurements spanning 40 days, net +41. 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 771–824 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 17:01818+13
8 Sept 2026, 09:58805+15
29 Aug 2026, 21:34790+2
23 Aug 2026, 10:48788+8
16 Aug 2026, 17:47780+3
8 Aug 2026, 01:48777no change
7 Aug 2026, 19:16777first reading

Engagement

15 posts held, back to 1 August 2026the 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 15 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
15s
Average length
15s

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.

Reaction mix

296 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 30.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8930.1%
🍓6823.0%
❤‍🔥5317.9%
💘268.78%
custom 5213218698155807974227.43%
196.42%
🥰93.04%
🔥72.36%
🎉20.676%
💋10.338%

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 14 of the 15 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 296 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 1 August 2026 to 7 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.

Recent posts

7 Aug 2026, 14:47 UTC74 views15 reactionsread 8 August 2026
Photo

ㅤ ㅤ ≡ 🤩 𝄀 𝐦𝐤 ◝ 𝑐𝑓𝑑𝑎𝑖𝑙𝑦 › › 〔 🤩 #sonya : #cassie : #johnny . 😻🤩 𝐜𝐫: lorithescrump on tumblr

🍓9❤‍🔥51

7 Aug 2026, 14:29 UTC81 views13 reactionsread 8 August 2026
Photo

◟ ⋮ #take / 𝐛𝐨𝐭 Старая история Ашры би лайк: Тгк нету, но есть твиттер: @San_san_ks🦭🦋 𔓕‌ . 𝐦𝐨𝐫𝐭𝐚𝐥 𝐤𝐨𝐦𝐛𝐚𝐭 ៸៸ 𝐝𝐚𝐢𝐥𝐲 𝐜𝐟

11🍓2

7 Aug 2026, 13:27 UTC88 viewsread 8 August 2026

◟ ⋮ #take / 𝐛𝐨𝐭 Йооу, в поисках активного флуда по мк, Напишите юз инфо мне сразу в личку— @V1t0rz 𔓕‌ . 𝐦𝐨𝐫𝐭𝐚𝐥 𝐤𝐨𝐦𝐛𝐚𝐭 ៸៸ 𝐝𝐚𝐢𝐥𝐲 𝐜𝐟

7 Aug 2026, 13:00 UTC88 views16 reactionsread 8 August 2026
Photo

ㅤ ㅤ ≡ 🤩 𝄀 𝐦𝐤 ◝ 𝑐𝑓𝑑𝑎𝑖𝑙𝑦 › › 〔 🤩 #sonya . 😻🤩 𝐜𝐫: zelt_rey on twitter

🍓122❤‍🔥1🔥1

7 Aug 2026, 12:07 UTC100 views19 reactionsread 8 August 2026
Photo

ㅤ ≡ 🤩 𝄀 𝐦𝐤 ◝ 𝑐𝑓𝑑𝑎𝑖𝑙𝑦 › › 〔 🤩 #ermac : #takeda : #kenshi . 😻🤩 𝐜𝐫: Druid_049 on twitter

113🍓2💋1💘1custom 52132186981558079741

7 Aug 2026, 11:00 UTC99 views17 reactionsread 8 August 2026
Photo

ㅤ ≡ 🤩 𝄀 𝐦𝐤 ◝ 𝑐𝑓𝑑𝑎𝑖𝑙𝑦 › › 〔 🤩 #mileena : #kunglao . 😻🤩 𝐜𝐫: hvnnybvnnii on tumblr

7custom 521321869815580797452🎉2🍓1

7 Aug 2026, 10:03 UTC105 views14 reactionsread 8 August 2026
Photo

ㅤ ㅤ ≡ 🤩 𝄀 𝐦𝐤 ◝ 𝑐𝑓𝑑𝑎𝑖𝑙𝑦 › › 〔 🤩 #sektor : #cyrax . 😻🤩 𝐜𝐫: tomietom473 on tumblr

7💘3🍓21❤‍🔥1

7 Aug 2026, 05:58 UTC114 views14 reactionsread 8 August 2026
Photo

◟ ⋮ #take / 𝐛𝐨𝐭 всем привет, я живой ханзоляни моя римская империя фор рил подпишитесь пж @gera_naorgani 𔓕‌ . 𝐦𝐨𝐫𝐭𝐚𝐥 𝐤𝐨𝐦𝐛𝐚𝐭 ៸៸ 𝐝𝐚𝐢𝐥𝐲 𝐜𝐟

6🍓4💘21custom 52132186981558079741

5 Aug 2026, 10:24 UTC152 views41 reactionsread 8 August 2026
Photo

◟ ⋮ #take / 𝐛𝐨𝐭 Скорпион одобряет Неанон ФрикФрида 𔓕‌ . 𝐦𝐨𝐫𝐭𝐚𝐥 𝐤𝐨𝐦𝐛𝐚𝐭 ៸៸ 𝐝𝐚𝐢𝐥𝐲 𝐜𝐟

❤‍🔥20🍓9💘74🔥1

4 Aug 2026, 04:16 UTC194 views38 reactionsread 8 August 2026
Photo

◟ ⋮ #take / 𝐛𝐨𝐭 Очень очень старые штучки 👀 Тгк: @boxmacandcheese 𔓕‌ . 𝐦𝐨𝐫𝐭𝐚𝐥 𝐤𝐨𝐦𝐛𝐚𝐭 ៸៸ 𝐝𝐚𝐢𝐥𝐲 𝐜𝐟

18💘13🍓42🔥1

3 Aug 2026, 17:41 UTC202 views23 reactionsread 8 August 2026
Photo

◟ ⋮ #take / 𝐛𝐨𝐭 привет соц опрос с какой части вам мк больше всего нравится неанон: Хантер / @zer0hunter 𔓕‌ . 𝐦𝐨𝐫𝐭𝐚𝐥 𝐤𝐨𝐦𝐛𝐚𝐭 ៸៸ 𝐝𝐚𝐢𝐥𝐲 𝐜𝐟

🍓1073custom 52132186981558079743

3 Aug 2026, 10:29 UTC203 views34 reactionsread 8 August 2026
Photo

◟ ⋮ #take / 𝐛𝐨𝐭 пррр @c31tjade 𔓕‌ . 𝐦𝐨𝐫𝐭𝐚𝐥 𝐤𝐨𝐦𝐛𝐚𝐭 ៸៸ 𝐝𝐚𝐢𝐥𝐲 𝐜𝐟

custom 521321869815580797412❤‍🔥11🍓532🔥1

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

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.

Mentions

Named by 1 registered channel — 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.

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

“Mortal Kombat | confession & daily!” (@mortalkombatcfdaily), 818 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/mortalkombatcfdaily.

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.