Telegram RegisterThe public register of Telegram

Channel

사랑 by MiMin ⌗ we made

@miminqueenn

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,096subscribers

+5 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003415197759
TypeChannel
Username@miminqueenn
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/miminqueenn

Growth

1,0911,0961,093.510 August 2026 — 1,091 subscribers10 August 2026 — 1,091 subscribers13 August 2026 — 1,096 subscribers10 August 202613 August 2026
3 measurements spanning 3 days, net +5. 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 1,090–1,097 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 08:531,096+5
10 Aug 2026, 14:001,091no change
10 Aug 2026, 13:461,091first reading

Engagement

10 posts held, back to 8 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.9%
avg views ÷ 1,096 subscribers
Avg views / post
284
10 posts measured
Reaction rate
20.9%
reactions ÷ views · ER floor
Posts in window
10
of 10 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held10 (8 August 202610 August 2026)
Views total2,842
Reactions total595
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 14:00 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

Video runtime
2m 26s
Average length
37s

Measured directly from 4 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

595 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 45.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 535078316775207466726945.2%
custom 528551172941601806617429.2%
custom 525606131905597509015225.5%

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

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

10 Aug 2026, 11:45 UTC114 views24 reactionsread 10 August 2026
Photo

МОЯ САМАЯ САМАЯ 😭

custom 528551172941601806612custom 52560613190559750906custom 53507831677520746676

Signed Алина

10 Aug 2026, 10:41 UTC151 views41 reactionsread 10 August 2026
Photo

покажите мне такого человека который её не любит 🫥

custom 525606131905597509021custom 528551172941601806610custom 535078316775207466710

Signed Алина

10 Aug 2026, 10:40 UTC149 views33 reactionsread 10 August 2026
Photo

олицетворение свободы ♡

custom 525606131905597509015custom 52855117294160180669custom 53507831677520746679

Signed Алина

9 Aug 2026, 15:02 UTC265 views56 reactionsread 10 August 2026

RUN AWAY

custom 535078316775207466731custom 528551172941601806615custom 525606131905597509010

Signed Алина

9 Aug 2026, 10:26 UTC360 views91 reactionsread 10 August 2026
Photo

У МИЁН ТЕПЕРЬ ТОЖЕ ТТ АККАУНТ

custom 535078316775207466748custom 528551172941601806622custom 525606131905597509021

Signed Алина

8 Aug 2026, 15:31 UTC355 views67 reactionsread 10 August 2026

тизер клипа на run away !

custom 535078316775207466730custom 528551172941601806619custom 525606131905597509018

Signed Алина

8 Aug 2026, 13:23 UTC434 views86 reactionsread 10 August 2026
Video

Я РЕВУ 😭😭😭😭😭😭

custom 535078316775207466744custom 528551172941601806623custom 525606131905597509019

Signed Алина

8 Aug 2026, 13:13 UTC350 views78 reactionsread 10 August 2026
Video

миён и сана были вместе на концерте эспа 👩‍❤️‍👩

custom 535078316775207466741custom 525606131905597509019custom 528551172941601806618

Signed Алина

8 Aug 2026, 03:45 UTC341 views62 reactionsread 10 August 2026
Video

миён рассказала, что песня «Run Away» изначально должна была войти в её второй альбом, но в итоге её исключили, так как она оказалась слишком жизнерадостной для общего настроения альбома. они даже пытались изменить аранжировку, чтобы сделать звучание чуть более сдержанным, но это не помогло. кроме того, с самого начала ей казалось, что песне больше подошел бы японский текст, и в итоге она сама приняла участие в его н

custom 535078316775207466737custom 528551172941601806613custom 525606131905597509012

Signed Алина

8 Aug 2026, 03:43 UTC323 views57 reactionsread 10 August 2026
Video

🐰: на самом деле, мы готовим и много всего другого. как знают небобо, я снова буду сниматься в дораме — впервые за очень долгое время. так что мы планируем усердно работать как над групповой, так и над сольной деятельностью

custom 528551172941601806633custom 535078316775207466713custom 525606131905597509011

Signed Алина

Showing the 10 most recent of 10 posts we hold for @miminqueenn. 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

Citation-graph rank — 1,048,609 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.

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

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

“사랑 by MiMin ⌗ we made” (@miminqueenn), 1,096 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/miminqueenn.

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.