Telegram RegisterThe public register of Telegram
Telegram profile photo for ᶫᶦᶠᵉ 𓈒◌| ⌗ 𝓶𝓲𝓻𝓮𝓲𝓽𝓸🪼 𝆹𝅥

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.

Register entry

Telegram ID-1003600211811
TypeChannel
Username@MireitoLife
DescriptionЛайф канал нашего флуда. Инфо- @Mireitoinfoflood
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 September 2026
Last confirmed live28 September 2026
Measurements held2
On Telegramt.me/MireitoLife

Growth

2128 Sept 2026, 13:47 — 21 subscribers28 Sept 2026, 14:22 — 21 subscribers28 Sept 2026, 13:4728 Sept 2026, 14:22
2 measurements taken within a single day. 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 20–22 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Sept 2026, 14:2221no change
28 Sept 2026, 13:4721first reading

Engagement

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 · 30 days
110.5%
avg views ÷ 21 subscribers
Avg views / post
23.2
20 posts measured
Reaction rate
10.6%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 September 2026
Posts held20 (12 September 2026 – 27 September 2026)
Views total464
Reactions total32
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 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.

What this channel posts

Photos
10
Videos
25
Links
7

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.

Video runtime
1m 36s
Average length
16s

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.

Reaction mix

32 reactions across 13 posts, in 14 distinct kinds. The most used accounts for 15.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5402607407081757588515.6%
custom 5400047099767202407412.5%
custom 522201847196500533839.38%
custom 522218912390058121839.38%
custom 522460953124540147139.38%
custom 531876233113453197939.38%
custom 539989347737695640426.25%
custom 540020232847521472826.25%
custom 540033484110119793726.25%
custom 522209368543229657413.13%
custom 522242155035076646013.13%
custom 540003029356017125013.13%
custom 540015250255961158013.13%
custom 540216556661615102213.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.

Recent posts

27 Sept 2026, 10:54 UTC9 views2 reactionsread 28 September 2026

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

custom 53998934773769564041custom 54026074070817575881

27 Sept 2026, 10:52 UTC10 views2 reactionsread 28 September 2026
Video

╔═════★ °:. *₊ ° . ☆ °:.╗ 𝑵𝑬𝑾 𝑽𝑰𝑫𝑬𝑶 ╚═════★ °:. *₊ ° . ☆ °:.╝ 𝗜𝗗: not ours. От младшего админа. 𝗧𝗶𝗸𝗧𝗼𝗸: @bloodyshineflood #video_MRT

custom 54000302935601712501custom 54003348411011979371

26 Sept 2026, 12:30 UTC15 views2 reactionsread 28 September 2026
Video

╔═════★ °:. *₊ ° . ☆ °:.╗ 𝑵𝑬𝑾 𝑽𝑰𝑫𝑬𝑶 ╚═════★ °:. *₊ ° . ☆ °:.╝ 𝗜𝗗: not ours. От владельца. 𝗧𝗶𝗸𝗧𝗼𝗸: @bloodyshineflood #video_MRT

custom 54000470997672024071custom 54026074070817575881

26 Sept 2026, 10:37 UTC13 views1 reactionsread 28 September 2026
Photo

༺═══════════༻ 𝘕𝘌𝘞 𝘜𝘕𝘐𝘖𝘕 ༺═══════════༻ сегодня флуд «𝅄𓈒◌| ⌗ 𝓶𝓲𝓻𝓮𝓲𝓽𝓸🪼» и флуд «𝘏𝘢𝘷𝘦𝘯 𝘧𝘭𝘰𝘰𝘥 » заключили дружеский союз. ───── ༺ ༻ ───── Название: 𝘏𝘢𝘷𝘦𝘯 𝘧𝘭𝘰𝘰𝘥 Инфо: @havenf_info Лайф: @haven_lifee следящий: @havenchat_bot ───── ༺ ༻ ───── 🔤удем надеяться на теплый и продуктивный союз ───── ☾ ───── [26.09.26] #union_MRT

custom 54001525025596115801

24 Sept 2026, 22:52 UTC23 viewsread 28 September 2026
Photo

🤩ейчас мы в активном поиске союзов,будем рады каждому. для заключения союза писать @Freks1xx #important_MRT

24 Sept 2026, 22:46 UTC21 viewsread 28 September 2026
Photo

༺═══════════༻ 𝘕𝘌𝘞 𝘜𝘕𝘐𝘖𝘕 ༺═══════════༻ сегодня флуд «𝅄𓈒◌| ⌗ 𝓶𝓲𝓻𝓮𝓲𝓽𝓸🪼» и флуд « 𝐒𝐧𝐚𝐤𝐞 𝐇𝐨𝐥𝐞» заключили дружеский союз. ───── ༺ ༻ ───── Название: 𝐒𝐧𝐚𝐤𝐞 𝐇𝐨𝐥𝐞 Инфо: @krdinfo229 Лайф: @krdlafe228 следящий: @d1no_d1 ───── ༺ ༻ ───── 🔤удем надеяться на теплый и продуктивный союз ───── ☾ ───── [25.09.26] #union_MRT

21 Sept 2026, 09:12 UTC31 views4 reactionsread 28 September 2026
Video

╔═════★ °:. *₊ ° . ☆ °:.╗ 𝑵𝑬𝑾 𝑽𝑰𝑫𝑬𝑶 ╚═════★ °:. *₊ ° . ☆ °:.╝ 𝗜𝗗: not ours. От младшего админа. 𝗧𝗶𝗸𝗧𝗼𝗸: @bloodyshineflood #video_MRT

custom 54026074070817575882custom 53998934773769564041custom 54000470997672024071

21 Sept 2026, 04:51 UTC29 views1 reactionsread 28 September 2026

рᥱп𑄜ст тᥲйм ₊˚⊹♡ 𝐺𝑜𝑙𝑑𝑒𝑛-𝐵𝑟𝑜𝑤𝑛 ♡⊹ [☀️] ˚₊ чᥙсткᥲ 𝑃𝑒︩︪𝑎𝑟𝑙 ¡ вᥙдᥱ𑄜 вᥙдᥱ𑄜 ᯓ ー 𝐃𝐑𝐄𝐃𝐖𝐀𝐑𝐃𝐒 ー . .𝄢₊˚⊹ вᥙдᥱ𑄜 вᥙдᥱ𑄜 вᥙдᥱ𑄜 вᥙдᥱ𑄜 вᥙдᥱ𑄜 вᥙдᥱ𑄜 Vanilla_flood 💛 чᥙсткᥲ #rp_MRT

custom 54000470997672024071

20 Sept 2026, 23:51 UTC24 views2 reactionsread 28 September 2026
Video

╔═════★ °:. *₊ ° . ☆ °:.╗ 𝑵𝑬𝑾 𝑽𝑰𝑫𝑬𝑶 ╚═════★ °:. *₊ ° . ☆ °:.╝ 𝗜𝗗: not ours. От владельца. 𝗧𝗶𝗸𝗧𝗼𝗸: @bloodyshineflood #video_MRT

custom 54002023284752147281custom 54026074070817575881

20 Sept 2026, 22:02 UTC22 viewsread 28 September 2026

༺═══════════༻ 𝘕𝘌𝘞 𝘜𝘕𝘐𝘖𝘕 ༺═══════════༻ сегодня флуд «𝅄𓈒◌| ⌗ 𝓶𝓲𝓻𝓮𝓲𝓽𝓸🪼» и флуд « ⸼࣪ 𓍢𓍢 ❬☾❭𝗦𝐨𝒯𝐭𝐞𝐫︩︪𝒮𝐢𝐬་༘࿐» заключили дружеский союз. ───── ༺ ༻ ───── Название: ⸼࣪ 𓍢𓍢 ❬☾❭𝗦𝐨𝒯𝐭𝐞𝐫︩︪𝒮𝐢𝐬་༘࿐ Инфо: @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.

Mentions

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.

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 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.