Telegram RegisterThe public register of Telegram

Channel

Mĩntœlikǎ пűшěт … ⁰²

@mintolika2

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

157subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003931391362
TypeChannel
Username@mintolika2
DescriptionВп 0+ / по поводу коллабораций в анонку По вп писать сюда: @hutohyt
CreatedBetween 1 April 2026 and 26 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
On Telegramt.me/mintolika2

Growth

1551571566 August 2026 — 155 subscribers7 August 2026 — 157 subscribers8 August 2026 — 157 subscribers6 August 20268 August 2026
3 measurements spanning 2 days, net +2. 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 155–157 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 18:16157no change
7 Aug 2026, 21:31157+2
6 Aug 2026, 21:46155first reading

Engagement

11 posts held, back to 26 July 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
129.9%
avg views ÷ 157 subscribers
Avg views / post
204
11 posts measured
Reaction rate
29.9%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 8 August 2026
Posts held11 (26 July 20268 August 2026)
Views total2,244
Reactions total671
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 18:16 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
49
Links
24

Lifetime counters from Telegram’s own channel header, read 8 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.

Reaction mix

671 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 16.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 526500740951602031011116.5%
custom 530575768555831258410315.4%
custom 53729840684534523659113.6%
custom 52810022285035545038913.3%
custom 52804743168933362388813.1%
custom 52130317554092913948312.4%
custom 5305519478082141596466.86%
custom 5217468933367427083365.37%
custom 5285228940179307294243.58%

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

Measured over the 11 most recent posts we hold, published 26 July 2026 to 8 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 11 we hold a reading for · 18%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mintolika2. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 11 most recent posts we hold for this entry, published 26 July 2026 to 8 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

8 Aug 2026, 17:35 UTC15 views16 reactions1 Starread 8 August 2026
Photo

๋࣭ ⭑ — 𝕭 øt • причувствие ٓ Frøٌm: @mintolika2 ⩇⩇:⩇⩇ link c.ai TW: нету ‹𝟹 通り- буду рада послушать мнения на счет бота пишите в комм #смн ཐིཋྀ #бот ᰔᩚ #стекло (?)

custom 52804743168933362385custom 53057576855583125844custom 53729840684534523654custom 52174689333674270833

Signed геруша. . .

7 Aug 2026, 10:44 UTC66 views69 reactionsread 8 August 2026
Photo

๋࣭ ⭑ — [𝑆]ketch • он среди нас. ٓ Frøٌm: @mintolika2 00;00 l1nk tًًٍo reكad {𝒎𝒂𝒃𝒆 ⲅⲉⲣⲩⲱⲁ} TW: нету. <3 通り- буду рада послушать мнения на счет зарисовки пишите в комм. #кшнцв ᰔᩚ #зарисовка ཐིཋྀ #стекло

custom 526500740951602031023custom 537298406845345236518custom 528047431689333623815custom 52174689333674270835custom 53057576855583125843custom 52130317554092913942custom 52810022285035545032custom 53055194780821415961

Signed геруша. . .

6 Aug 2026, 08:56 UTC104 views19 reactionsread 8 August 2026

Типы пришло время моего ухода :(( Очень жаль но 😭😭😭😭😭😭😭 Я УЛЕТАЮ В ГРУЗИЮ НА НЕДЕЛЮ ЛОЛ писать ботов не выйдет пока я на отдыхе так что Гера будет отдуваться за меня еще дала админку Саше грей чтобы не скучали ПОТОМ ВЕРНУСЬ БУДКТ КОЛЛАБ С ЮЖНОЙ И ПАК БОТОВ ТИПЫ)) 😚

custom 537298406845345236511custom 52174689333674270834custom 53057576855583125844

Signed M1ntøتنlikâ

5 Aug 2026, 09:07 UTC210 views92 reactionsread 8 August 2026
Photo

🤩🤩ew Bot — ДТП •#мзлфф 🪦🪦🪦 / fr✅om: @mintolika2 🦇 💕- пишите мнения и ставьте реакции это лучшая поддержка 🪦 Bot c.ai 🤩 Bot chai 🤩 Bot sea soul 🤩

custom 528047431689333623827custom 526500740951602031019custom 528100222850355450319custom 52130317554092913946custom 53057576855583125846custom 52174689333674270835custom 53055194780821415965custom 53729840684534523655

Signed M1ntøتنlikâ

4 Aug 2026, 13:34 UTC282 views18 reactionsread 8 August 2026
Photo

🎀 🤩ссоциации от 🎀яты ✨ 🌟• 🎀для участия🔡нужно; 1. Быть🎀подписанным 🎀 2. Поставить🔡рк на закреп> 3. рп этот пост🎀 🤩 ⭐⭐⭐⭐⭐⭐⭐⭐ В замен вы получите от меня; 1. Какой🎀вы лабубу 2. Какая вы команта 🤩 Закрыто 🤩🤩

custom 526500740951602031015custom 52810022285035545033

Signed M1ntøتنlikâ

4 Aug 2026, 06:11 UTC184 views84 reactionsread 8 August 2026
Photo

🤩🤩ew Bot — квартира напротив•#гспд 🪦🪦🪦 / fr✅om: @mintolika2 🦇 💕- пишите мнения и ставьте реакции это лучшая поддержка 🪦 Bot c.ai 🤩 Bot chai 🤩 Bot sea soul 🤩

custom 526500740951602031025custom 521303175540929139417custom 537298406845345236516custom 53055194780821415966custom 53057576855583125846custom 52804743168933362385custom 52810022285035545035custom 52174689333674270834

Signed M1ntøتنlikâ

3 Aug 2026, 11:35 UTC173 views68 reactionsread 8 August 2026
Photo

🌺 — 🔹ot • потерянный друг ٓ Frøٌm: @mintolika2 😀😀link c.ai TW: нету 😶 ✨- буду рада послушать мнения на счет бота пишите в комм 🎠🎠 #дисаБебрина 🌺 #бот 👧 #флафф (?)

custom 528100222850355450319custom 530575768555831258418custom 521303175540929139417custom 52650074095160203104custom 53055194780821415964custom 52804743168933362383custom 53729840684534523653

Signed M1ntøتنlikâ

1 Aug 2026, 15:52 UTC230 views74 reactionsread 8 August 2026
Photo

🌺 — 🔹ot • сосед ٓ Frøٌm: @mintolika2 😀😀link c.ai TW: нету 😶 ✨- буду рада послушать мнения на счет бота пишите в комм 🎠🎠 #дк 🌺 #бот 👧 #флафф (?)

custom 528100222850355450319custom 530551947808214159619custom 521303175540929139416custom 52804743168933362385custom 53057576855583125845custom 52650074095160203104custom 52174689333674270833custom 53729840684534523653

Signed M1ntøتنlikâ

29 Jul 2026, 11:01 UTC352 views80 reactionsread 8 August 2026
Photo

๋࣭ ⭑ — 𝕭 øt • любовь у озера ٓ Frøٌm: @mintolika2 ⩇⩇:⩇⩇ link c.ai TW: нету ‹𝟹 通り- буду рада послушать мнения на счет бота пишите в комм #АкираУткин ཐིཋྀ #бот ᰔᩚ #флафф

custom 530575768555831258425custom 528047431689333623820custom 521303175540929139417custom 52174689333674270834custom 52810022285035545034custom 53055194780821415964custom 53729840684534523654custom 52650074095160203102

Signed ⁰²(miss.) геруша.🍧

28 Jul 2026, 08:09 UTC320 views76 reactions1 Starread 8 August 2026
Photo

๋࣭ ⭑ — 𝕭 øt • слезное прощение ٓ Frøٌm: @mintolika2 ⩇⩇:⩇⩇ link c.ai TW: бытовая ссора ‹𝟹 通り- буду рада послушать мнения на счет бота пишите в комм #медкид ཐིཋྀ #бот ᰔᩚ #флафф

custom 537298406845345236527custom 530575768555831258416custom 526500740951602031015custom 52130317554092913944custom 52174689333674270834custom 52810022285035545034custom 52804743168933362383custom 53055194780821415963

Signed ⁰²рестт до августа//(miss.) геруша.🍧

26 Jul 2026, 18:27 UTC308 views75 reactionsread 8 August 2026
Photo

🌺 — 🔹ot • девочка с каре ٓ Frøٌm: @mintolika2 😀😀link c.ai TW: суицидальные наклонности 😶 ✨- буду рада послушать мнения на счет бота пишите в комм 🎠🎠 #мазюши 🌺 #бот 👧 #стекло

custom 528522894017930729424custom 530575768555831258416custom 528100222850355450314custom 52804743168933362385custom 52130317554092913944custom 52174689333674270834custom 52650074095160203104custom 53055194780821415964

Signed M1ntøتنlikâ

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 21,430 of 1,176,251entries 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Mĩntœlikǎ пűшěт … ⁰²” (@mintolika2), 157 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/mintolika2.

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.