File, posted without a caption
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡

Channel
@Kohska_Misa
On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
24subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003815319484 |
|---|---|
| Type | Channel |
| Username | @Kohska_Misa |
| Description | Приветик! Это хатка Мисы, тут будет очень много всего! Мы очень стараемся над контентом!♡ Мечта 50+ |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Kohska_Misa |
@Kohska_Misa was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 10:48 | 24 | no change |
| 9 Aug 2026, 03:46 | 24 | first reading |
15 posts held, back to 9 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 pageof Telegram’s post history, 20 posts per page.
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 8 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 15 (9 August 2026 – 11 August 2026) |
| Views total | 104 |
| Reactions total | 18 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 10:48 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.
Lifetime counters from Telegram’s own channel header, read 11 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.
18 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5420597779544166327 | 6 | 33.3% | |
| custom 5417850525188117423 | 4 | 22.2% | |
| custom 5420412735173185986 | 3 | 16.7% | |
| custom 5433713157967224484 | 3 | 16.7% | |
| custom 5420295499745875389 | 1 | 5.56% | |
| 💘 | 1 | 5.56% |
Custom emoji. 5 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 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 8 of the 15 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 18reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 9 August 2026 to 11 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.
File, posted without a caption
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Sticker, posted without a caption
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Блин, может на 25 подписчиков сделать реквесты?
custom 54178505251881174231
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Что бы она с вами сделала? Она потрогает ваш хвостик! 5/5
custom 54204127351731859863
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Что бы она с вами сделала? Она потрогает ваши пряди и удивляется! 4/5
custom 54337131579672244843
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Что бы она с вами сделала? Она попыталась стереть кровь с щеки! 3/5
custom 54205977795441663273custom 54202954997458753891
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Что бы она с вами сделала? Она потрогала ваши ушки,а потом обняла! 2/5
custom 54178505251881174232
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Жду себя день первый
💘1
Signed ✿Secret Agent_Head Nurse✿✿
Что бы она с вами сделала? Она потрогала ваши рожки, а потом ваши крылышки! 1/5
custom 54205977795441663273
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Я наверное буду делать когда будет 5😔
custom 54178505251881174231
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Что мой персонаж сделает с вами? Скидывайте своих персонажей под этот пост! Мест 5/5
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Такс такс такс
Signed [💕]-𝑲𝒐𝒔𝒉𝒌𝒂 𝑳𝒂𝒏𝒂♰ᥱs𝖿⍴#хочуспать¡
Showing the 12 most recent of 15 posts we hold for @Kohska_Misa. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Что вы хотите??
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 15 most recent posts we hold, published 9 August 2026 to 11 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Хатка Мисы” (@Kohska_Misa), 24 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Kohska_Misa.
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.