Channel
@MR_liife
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
68subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003479228378 |
|---|---|
| Type | Channel |
| Username | @MR_liife |
| Description | 𝐋𝐢𝐟𝐞: @MR_liife 𝐈𝐧𝐟𝐨: @MR_inffo 𝐒𝐭𝐚𝐫𝐭: 11.11.25 |
| Created | Between 1 November 2025 and 11 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/MR_liife |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 03:00 | 68 | no change |
| 12 Aug 2026, 02:49 | 68 | first reading |
16 posts held, back to 11 February 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 18 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 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.
81 reactions across 10 posts, in 13 distinct kinds. The most used accounts for 21.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5426907155221455893 | 17 | 21.0% | |
| custom 5395440210471297453 | 12 | 14.8% | |
| custom 5454134361660081647 | 11 | 13.6% | |
| custom 5267325313171351700 | 8 | 9.88% | |
| custom 5402521799793581450 | 8 | 9.88% | |
| custom 5470075996067603435 | 6 | 7.41% | |
| custom 5296727954905131242 | 4 | 4.94% | |
| custom 5357462172609831786 | 4 | 4.94% | |
| custom 5325729339319281627 | 3 | 3.70% | |
| custom 5408995187387015251 | 3 | 3.70% | |
| custom 5420141555233071341 | 3 | 3.70% | |
| custom 5265030739778369074 | 1 | 1.23% | |
| custom 5298495187918547416 | 1 | 1.23% |
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 10 of the 16 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 81reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 11 February 2026 to 18 March 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.
Привет ребят ожидается нью эра. Внимание, постер от Лазо. ❤️❤️❤️❤️
custom 54269071552214558939custom 53954402104712974536custom 54025217997935814504custom 54201415552330713412custom 54700759960676034352
✮ 🌟 ﹫𝐏𝗁𝖺𝗂𝗇𝗈𝗇⠀Avery𝆟 : ᭥ ࿙࿚ вам снился этот человек? ♱ ✮ 🐈⬛ ﹫𝐉𝐚𝐝𝐞⠀Darcy𝆟 : ᭥ ࿙࿚ нихуя подгон. 🔥🔥♱
✮ 🐈⬛ ﹫𝐉𝐚𝐝𝐞⠀Darcy𝆟 : ᭥ ࿙࿚ это вайб. ♱
custom 54269071552214558934custom 54025217997935814503custom 54541343616600816473
✮ 🌟 @𝐏𝗁𝖺𝗂𝗇𝗈𝗇𝄒 Avery𝆟 : ᭥ ࿙࿚ победители конкурса определены, правда из-за некоторых неполадок призы выдадут к концу месяца. надеемся на ваше понимание, всех целую!🌟🌟
custom 53954402104712974534custom 54541343616600816472custom 54700759960676034352
Sticker, posted without a caption
custom 54541343616600816474
✮ 🐺 ﹫𝐉𝐚𝐝𝐞⠀Darcy𝆟 : ᭥ ࿙࿚ Неужели это случилось ребят. Вышло интервью. Бонус фулл этого интервью. ♱ ✮ 🌟 @𝐂𝐢𝐩𝐡𝐞𝐫𝄒 Vieno𝆟 : ᭥ ࿙࿚ WAR IS OVER. . . ♱ ✮ ⭐ @𝐍𝐞𝐮𝐯𝐢𝐥𝐥𝐞𝐭𝐭𝐞𝄒 Azray𝆟 : ᭥ ࿙࿚ возьми телефон детка... ♱
custom 54089951873870152513custom 53954402104712974532custom 54700759960676034352custom 54025217997935814501
⭐️⭐️...ㅤۗㅤ𝗜 . 𝗡𝖳𝖤𝗥𝖵𝖨𝗘𝖶⠀: 𝟯𝟮🅨 𝁒⠀ ⭐️⭐️⠀♱ © 𝟎𝟣. 🖤 M𝓔𝗠ִ𝖮֗RI𝗘𝒮 ㅤ.ㅤ❪ 不！Приветствуем вас, ♟ уважаемые читатели. Наша редакция подготовила для вас ⌨ нечто интересное. ㅤㅤㅤㅤ፝ 📰 Напоминаем, у каждого желающего была возможность задать интересующий вопрос главному виновнику торжества, и сегодня мы узнаем ответы. ㅤ.ㅤ❪ ᩧ🤩редставляем вашему вниманию долгожданное интервью с Данфером, владельцем ᯓ ☾ 𝐓𝐇𝐄 𝐖𝐎𝐋𝐅 𝐏𝐀𝐂𝐊 ☽. ㅤㅤ⭐⭐…
custom 54269071552214558934
✮ 🐺 ﹫𝐉𝐚𝐝𝐞⠀Darcy𝆟 : ᭥ ࿙࿚ ауф. ♱
ㅤㅤㅤㅤ ᯓ ☾ 𝐓𝐇𝐄 𝐖𝐎𝐋𝐅 𝐏𝐀𝐂𝐊 ☽ ㅤ ㅤㅤ ㅤ исполнился 1 год. ⟡ | 𝐁𝐥𝐚𝐝𝐞 – Сегодня нашему флуду исполнился целый год. Мне сложно подобрать слова, чтобы описать эмоции на данный момент, но я невероятно счастлив. За год мы добились много всего. Мы падали, поднимались вновь и заново запускали стрелки часов. Ругались, веселились, много работали. Каждый вложил частичку в этот проект. Хочу поблагодарить в первую очередь администраци…
Sticker, posted without a caption
Ребят, мы пять часов уже проводим интервью. Скорее всего статья будет уже завтра. Убейте меня пожалуйста.
custom 54541343616600816472custom 54201415552330713411
ㅤ🐾🐾𓏼 🤍𝒐𝒍𝒍𝒂𝒈𝒆𝒔 ᥬᩤּׅ ׅ 🐾 ㅤㅤㅤ 🤩а тему: любовь и ее восприятие в античности. ㅤ🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸 ㅤ （💕）. 🤍𝒐𝒓𝒆 𝒂𝒃𝒐𝒖𝒕.^᪲᪲ ㅤㅤㅤ🤩ы проводим интерактив совместно с проектом Deonis. Обязательно загляните к ним! ㅤ （💕） . 🤍𝒐𝒓𝒎.^᪲᪲᪲ ㅤㅤ1. Подписка на инфо нашего партнера — @DNS1nfo. ㅤㅤ2. Псевдоним или название проекта в моно. ㅤㅤ3. Юзернейм ссылкой/инфо ссылкой. ㅤ🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸 ㅤ（💕）. 🤩𝒐𝒓𝒆 𝒂𝒃𝒐𝒖𝒕.^᪲᪲ ㅤㅤㅤ🤍оличество мест — 7/10. ㅤ🌸🌸🌸🌸🌸🌸🌸🌸🌸🌸 ㅤ #𝒊𝒏𝒕𝒆
Showing the 12 most recent of 16 posts we hold for @MR_liife. 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 — 1,255,799 of 1,345,403entries 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.
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.
Named by 2 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“﹙ 路 𝟬𝟵 𝗅︩︪𝗂𝗳𝖾 : M͠𝓔𝗠ִ𝖮֗R͟I͟𝗘𝓢” (@MR_liife), 68 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/MR_liife.
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.