3 measurements spanning 32 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 260–261 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Sept 2026, 10:23
260
no change
22 Aug 2026, 14:39
260
-1
7 Aug 2026, 16:23
261
first reading
Engagement
9 posts held, back to 29 August 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
49.1%
avg views ÷ 260 subscribers
Avg views / post
128
9 posts measured
Reaction rate
15.2%
reactions ÷ views · ER floor
Posts in window
9
of 9 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
Window
Rolling 30 days · latest post in window 8 September 2026
Posts held
9 (29 August 2026 – 8 September 2026)
Views total
1,148
Reactions total
174
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Sept 2026, 10:23 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
≈1,230
Videos
≈291
Links
≈76
Lifetime counters from Telegram’s own channel header, read 8 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
31s
Average length
8s
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
174 reactions across 9 posts, in 12 distinct kinds. The most used accounts for 26.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5249305996924311948
46
26.4%
custom 5348177149100572342
32
18.4%
custom 5246922234240447583
23
13.2%
custom 5393366269548315735
22
12.6%
custom 5188465465894126644
16
9.20%
custom 5244916003476886568
15
8.62%
custom 5341779889802462621
9
5.17%
custom 5100333784952210184
3
1.72%
custom 5251414185916521083
3
1.72%
custom 5321444933347854610
2
1.15%
custom 5415936129415277374
2
1.15%
custom 5186315658668803264
1
0.575%
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 9 of the 9 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 174 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 29 August 2026 to 8 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.
Telegram Stars
Stars received
7
across the posts below
Posts paid on
6
of 9 we hold a reading for · 67%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mileeeshiikk. 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 9 most recent posts we hold for this entry, published 29 August 2026 to 8 September 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.
Примеряю на себя роль тревел блогера и делюсь хайлайтами и своими рекомендациями от прошедшего вакейшена:
Отель – Novva Kaş. Очень уютный и спокойный отель с классными номерами и хорошей атмосферой. Персонал местами был невнимательным, но в остальном отличный вариант для тех, кто хочет действительно отдохнуть, а не составлять расписание из завтраков, походов по всем достопримечательностям и планами как составить пл…
В этот маленький отпуск я улетела случайно.
Мега спонтанно, что, будь у меня время адекватно обмозговать, аргумент в пользу того чтобы остаться дома, наверное бы перевесил…
Времени на это не было. (спасибо девочкам)
Поэтому,
накручивая себя первые часы полета мыслями о том, что никакого отдыха я не заслужила и мой удел — только вклалыватьработать, я расслабилась.
Так начался один из самых роскошных отпусков в моей …
Kaş & Co 🌚🌟
ловим последние тёплые дни лета.
люблю эту нашу странную особенность с девочками - не можем встретиться в Москве, зато стабильно живём вместе в поездках по две недели, словно никаких длительных промежутков между нами и не было.
много смеёмся, плаваем, гуляем, снимаем всё вокруг и подтягиваем мой турецкий.
потом обратно домой и кто куда ;
работать, готовиться к сессии и снова работать.
но пока не об этом
Showing the 9 most recent of 9 posts we hold for @mileeeshiikk. 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.
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 September 2026 — this
entry's latest reading, not the date you are reading this.
“mi<3” (@mileeeshiikk), 260 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/mileeeshiikk.
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.
