Telegram RegisterThe public register of Telegram
Telegram profile photo for архив - да, я кинню и .. | MHA

Channel

архив - да, я кинню и .. | MHA

@mhakinn

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

69subscribers

-1 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002784967589
TypeChannel
Username@mhakinn
CreatedBetween 1 June 2025 and 18 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live17 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/mhakinn

Growth

68706911 August 2026 — 70 subscribers12 August 2026 — 70 subscribers25 August 2026 — 69 subscribers10 September 2026 — 68 subscribers17 September 2026 — 69 subscribers11 August 202617 September 2026
5 measurements spanning 37 days, net -1. 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 68–70 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 20:3869+1
10 Sept 2026, 06:3868-1
25 Aug 2026, 04:0669-1
12 Aug 2026, 11:0870no change
11 Aug 2026, 17:4670first reading

Engagement

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

Reaction mix

559 reactions across 18 posts, in 25 distinct kinds. The most used accounts for 22.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 526735094983114330212522.4%
9116.3%
custom 54474057714048961828214.7%
custom 5447640800605268363427.51%
407.16%
👾244.29%
custom 5262772166801258862213.76%
custom 5447129098201624814193.40%
💘193.40%
🕊193.40%
❤‍🔥162.86%
🍓142.50%
custom 526525441738016836071.25%
custom 585954817024931163071.25%
💋71.25%
👎40.716%
🥰40.716%
custom 538686538986922136630.537%
🔥30.537%
🤔30.537%
5 further kinds91.61%

Custom emoji. 8 of the rows above are 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 18 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 559 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 18 August 2025 to 26 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.

Recent posts

26 Mar 2026, 19:50 UTC128 views25 reactionsread 11 August 2026

😰 . юлять канал продать не получится да

❤‍🔥125👎4💔2👾1🔥1

27 Aug 2025, 09:58 UTC802 views30 reactionsread 11 August 2026
Photo

ㅤ﹙↺﹚ - да , я кинню ла браву и надо мной издевались в школе и считали странным(-ой) . ⇅ да, я кинню и ..|@mhakinn ⟡ предложить идею !! ⎯⎯⎯⎯⎯

11custom 52673509498311433028custom 54474057714048961826custom 544712909820162481432

27 Aug 2025, 09:42 UTC764 views26 reactionsread 11 August 2026
Photo

ㅤ﹙↺﹚ - да , я кинню яойорозу и я часто сомневаюсь в том что заслуживаю ли я то что имею ведь меня преследуют мысли о том , что на самом деле я совсем не так хорош(-а) , как обо мне принято думать . ⇅ да, я кинню и ..|@mhakinn ⟡ предложить идею !! ⎯⎯⎯⎯⎯

custom 526735094983114330296💘6custom 544740577140489618231custom 54471290982016248141

26 Aug 2025, 11:42 UTC896 views34 reactionsread 11 August 2026
Photo

ㅤ﹙↺﹚ - да , я кинню хизаши и я очень шумный – меня часто просят быть тише на публике , хотя громкостью своего голоса я лишь показываю , что чувствую прямо сейчас . ⇅ да, я кинню и ..|@mhakinn ⟡ предложить идею !! ⎯⎯⎯⎯⎯

custom 526735094983114330297custom 54476408006052683637custom 54474057714048961825💘21👾1🕊1

26 Aug 2025, 11:03 UTC862 views37 reactionsread 11 August 2026
Photo

ㅤ﹙↺﹚ - да , я кинню айзаву и для меня мои близкие , подопечные и коллеги – важнее всего и я всегда встану на их защиту . ⇅ да, я кинню и ..|@mhakinn ⟡ предложить идею !! ⎯⎯⎯⎯⎯

custom 52673509498311433021211custom 544740577140489618243❤‍🔥1👾1💯1🔥1

24 Aug 2025, 15:52 UTC676 views29 reactionsread 11 August 2026
Photo

ㅤ﹙↺﹚ - да , я кинню химико и я хочу любви , и мне неважно от кого она . ⇅ да, я кинню и ..|@mhakinn ⟡ предложить идею !! ⎯⎯⎯⎯⎯

custom 52673509498311433029custom 54474057714048961826💋4custom 54471290982016248144💘211👾1

24 Aug 2025, 05:33 UTC818 views30 reactionsread 11 August 2026
Photo

ㅤ﹙↺﹚ - да , я кинню айзаву и если узнать меня получше то станет очевидно что я гораздо мягче , чем могу показаться . ⇅ да, я кинню и ..|@mhakinn ⟡ предложить идею !! ⎯⎯⎯⎯⎯

👾7custom 544764080060526836363❤‍🔥3custom 54474057714048961823💘2🤝21

24 Aug 2025, 05:04 UTC747 views20 reactionsread 11 August 2026
Photo

ㅤ﹙↺﹚ - да , я кинню серо и у меня великолепное чувства юмора и меня часто любят по большей части за мои шутки . ⇅ да, я кинню и ..|@mhakinn ⟡ предложить идею !! ⎯⎯⎯⎯⎯

custom 526735094983114330274👾4💋21🕊1🥱1

23 Aug 2025, 19:40 UTC793 views25 reactionsread 11 August 2026
Photo

ㅤ﹙↺﹚ - да , я кинню ястреба и мне нравится подшучивать над некоторыми и доставать их повседневными вопросами . ⇅ да, я кинню и ..|@mhakinn ⟡ предложить идею !! ⎯⎯⎯⎯⎯

12🕊5custom 52673509498311433024custom 544740577140489618221custom 54476408006052683631

23 Aug 2025, 19:24 UTC518 views34 reactionsread 11 August 2026
Photo

ㅤ﹙↺﹚ - да , я кинню бакуго и ... ⇅ да, я кинню и ..|@mhakinn О1 . я люблю быть в центре внимания . О2 . я стремлюсь стать сильнейшим(-ей) доказывая это грубой силой . О3 . из-за постоянных похвал моих способностей в детстве у меня развился комплекс превосходства , из-за чего я хочу быть первым(-ой) и лучшим(-ей) во всём . ⟡ предложить идею !! ⎯⎯⎯⎯⎯

🍓129custom 52673509498311433023custom 54471290982016248142custom 54474057714048961822custom 544764080060526836321👾1

Showing the 12 most recent of 20 posts we hold for @mhakinn. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“архив - да, я кинню и .. | MHA” (@mhakinn), 69 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/mhakinn.

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.