╭── ⋅ ⋅ ── ✿ ── ⋅ ⋅ ──╮ nᴇw ᴩᴏsᴛ ╰── ⋅ ⋅ ── ✿ ── ⋅ ⋅ ──╯ я скоро буду деградировать,от таких видео мои мозги гниют. #shitpost_MRT
custom 53998934773769564041custom 54026074070817575881

Channel
@MireitoLife
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
21subscribers
+0 since we began measuring on 28 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003600211811 |
|---|---|
| Type | Channel |
| Username | @MireitoLife |
| Description | Лайф канал нашего флуда. Инфо- @Mireitoinfoflood |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/MireitoLife |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 14:22 | 21 | no change |
| 28 Sept 2026, 13:47 | 21 | first reading |
20 posts held, back to 12 September 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.
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 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 20 (12 September 2026 – 27 September 2026) |
| Views total | 464 |
| Reactions total | 32 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Sept 2026, 14:22 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.
Lifetime counters from Telegram’s own channel header, read 28 September 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 6 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.
32 reactions across 13 posts, in 14 distinct kinds. The most used accounts for 15.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5402607407081757588 | 5 | 15.6% | |
| custom 5400047099767202407 | 4 | 12.5% | |
| custom 5222018471965005338 | 3 | 9.38% | |
| custom 5222189123900581218 | 3 | 9.38% | |
| custom 5224609531245401471 | 3 | 9.38% | |
| custom 5318762331134531979 | 3 | 9.38% | |
| custom 5399893477376956404 | 2 | 6.25% | |
| custom 5400202328475214728 | 2 | 6.25% | |
| custom 5400334841101197937 | 2 | 6.25% | |
| custom 5222093685432296574 | 1 | 3.13% | |
| custom 5222421550350766460 | 1 | 3.13% | |
| custom 5400030293560171250 | 1 | 3.13% | |
| custom 5400152502559611580 | 1 | 3.13% | |
| custom 5402165566616151022 | 1 | 3.13% |
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 13 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 32 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 12 September 2026 to 27 September 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.
╭── ⋅ ⋅ ── ✿ ── ⋅ ⋅ ──╮ nᴇw ᴩᴏsᴛ ╰── ⋅ ⋅ ── ✿ ── ⋅ ⋅ ──╯ я скоро буду деградировать,от таких видео мои мозги гниют. #shitpost_MRT
custom 53998934773769564041custom 54026074070817575881
╔═════★ °:. *₊ ° . ☆ °:.╗ 𝑵𝑬𝑾 𝑽𝑰𝑫𝑬𝑶 ╚═════★ °:. *₊ ° . ☆ °:.╝ 𝗜𝗗: not ours. От младшего админа. 𝗧𝗶𝗸𝗧𝗼𝗸: @bloodyshineflood #video_MRT
custom 54000302935601712501custom 54003348411011979371
╔═════★ °:. *₊ ° . ☆ °:.╗ 𝑵𝑬𝑾 𝑽𝑰𝑫𝑬𝑶 ╚═════★ °:. *₊ ° . ☆ °:.╝ 𝗜𝗗: not ours. От владельца. 𝗧𝗶𝗸𝗧𝗼𝗸: @bloodyshineflood #video_MRT
custom 54000470997672024071custom 54026074070817575881
༺═══════════༻ 𝘕𝘌𝘞 𝘜𝘕𝘐𝘖𝘕 ༺═══════════༻ сегодня флуд «𝅄𓈒◌| ⌗ 𝓶𝓲𝓻𝓮𝓲𝓽𝓸🪼» и флуд «𝘏𝘢𝘷𝘦𝘯 𝘧𝘭𝘰𝘰𝘥 » заключили дружеский союз. ───── ༺ ༻ ───── Название: 𝘏𝘢𝘷𝘦𝘯 𝘧𝘭𝘰𝘰𝘥 Инфо: @havenf_info Лайф: @haven_lifee следящий: @havenchat_bot ───── ༺ ༻ ───── 🔤удем надеяться на теплый и продуктивный союз ───── ☾ ───── [26.09.26] #union_MRT
custom 54001525025596115801
🤩ейчас мы в активном поиске союзов,будем рады каждому. для заключения союза писать @Freks1xx #important_MRT
༺═══════════༻ 𝘕𝘌𝘞 𝘜𝘕𝘐𝘖𝘕 ༺═══════════༻ сегодня флуд «𝅄𓈒◌| ⌗ 𝓶𝓲𝓻𝓮𝓲𝓽𝓸🪼» и флуд « 𝐒𝐧𝐚𝐤𝐞 𝐇𝐨𝐥𝐞» заключили дружеский союз. ───── ༺ ༻ ───── Название: 𝐒𝐧𝐚𝐤𝐞 𝐇𝐨𝐥𝐞 Инфо: @krdinfo229 Лайф: @krdlafe228 следящий: @d1no_d1 ───── ༺ ༻ ───── 🔤удем надеяться на теплый и продуктивный союз ───── ☾ ───── [25.09.26] #union_MRT
😭
#repost 💙
╔═════★ °:. *₊ ° . ☆ °:.╗ 𝑵𝑬𝑾 𝑽𝑰𝑫𝑬𝑶 ╚═════★ °:. *₊ ° . ☆ °:.╝ 𝗜𝗗: not ours. От младшего админа. 𝗧𝗶𝗸𝗧𝗼𝗸: @bloodyshineflood #video_MRT
custom 54026074070817575882custom 53998934773769564041custom 54000470997672024071
рᥱп𑄜ст тᥲйм ₊˚⊹♡ 𝐺𝑜𝑙𝑑𝑒𝑛-𝐵𝑟𝑜𝑤𝑛 ♡⊹ [☀️] ˚₊ чᥙсткᥲ 𝑃𝑒︩︪𝑎𝑟𝑙 ¡ вᥙдᥱ𑄜 вᥙдᥱ𑄜 ᯓ ー 𝐃𝐑𝐄𝐃𝐖𝐀𝐑𝐃𝐒 ー . .𝄢₊˚⊹ вᥙдᥱ𑄜 вᥙдᥱ𑄜 вᥙдᥱ𑄜 вᥙдᥱ𑄜 вᥙдᥱ𑄜 вᥙдᥱ𑄜 Vanilla_flood 💛 чᥙсткᥲ #rp_MRT
custom 54000470997672024071
╔═════★ °:. *₊ ° . ☆ °:.╗ 𝑵𝑬𝑾 𝑽𝑰𝑫𝑬𝑶 ╚═════★ °:. *₊ ° . ☆ °:.╝ 𝗜𝗗: not ours. От владельца. 𝗧𝗶𝗸𝗧𝗼𝗸: @bloodyshineflood #video_MRT
custom 54002023284752147281custom 54026074070817575881
༺═══════════༻ 𝘕𝘌𝘞 𝘜𝘕𝘐𝘖𝘕 ༺═══════════༻ сегодня флуд «𝅄𓈒◌| ⌗ 𝓶𝓲𝓻𝓮𝓲𝓽𝓸🪼» и флуд « ⸼࣪ 𓍢𓍢 ❬☾❭𝗦𝐨𝒯𝐭𝐞𝐫︩︪𝒮𝐢𝐬་༘࿐» заключили дружеский союз. ───── ༺ ༻ ───── Название: ⸼࣪ 𓍢𓍢 ❬☾❭𝗦𝐨𝒯𝐭𝐞𝐫︩︪𝒮𝐢𝐬་༘࿐ Инфо: @sotterlis_info Лайф: @sotterlis_Life следящий: @anon_sundaybot ───── ༺ ༻ ───── 🔤удем надеяться на теплый и продуктивный союз ───── ☾ ───── [] #union_MRT
Showing the 12 most recent of 20 posts we hold for @MireitoLife. 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.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“ᶫᶦᶠᵉ 𓈒◌| ⌗ 𝓶𝓲𝓻𝓮𝓲𝓽𝓸🪼 𝆹𝅥” (@MireitoLife), 21 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/MireitoLife.
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.