Channel
@katecoronadowrite
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
94subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001661630305 |
|---|---|
| Type | Channel |
| Username | @katecoronadowrite |
| Description | Локальные приколы, самые свежие новости и просто бормочение ни о чём и обо всём 🤭 ВСЁ ВАЖНОЕ В ЗАКРЕПЕ! |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/katecoronadowrite |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 13:15 | 94 | no change |
| 9 Aug 2026, 03:52 | 94 | -1 |
| 8 Aug 2026, 11:47 | 95 | first reading |
20 posts held, back to 15 May 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 6 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (15 May 2026 – 8 August 2026) |
| Views total | 384 |
| Reactions total | 20 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 13:15 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 9 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.
104 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 26 | 25.0% | |
| 😍 | 25 | 24.0% | |
| 🔥 | 15 | 14.4% | |
| custom 5334659877702755319 | 10 | 9.62% | |
| 🎉 | 9 | 8.65% | |
| 🤩 | 7 | 6.73% | |
| 💔 | 6 | 5.77% | |
| custom 5334831302732438999 | 3 | 2.88% | |
| 🍓 | 3 | 2.88% |
Custom emoji. 2 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 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 104reactions 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 15 May 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.
— Мы всё потеряли, — медленно проговаривает Женя, клеймя ситуацию безнадёжной. Клименко прикрывает глаза, чувствуя вину, злость, боль и, наконец, долгожданное облегчение от того, что всё наконец-таки всплыло на поверхность. Какое-то время он молчит, глядя куда угодно, но мимо Мурашовой, а потом поднимает глаза. Максим прикусывает губу от понимания, что ещё чуть-чуть и сорвётся, коснётся её как в последний раз. Держи…
💔3
ㅤЯ привычно не уследила, что у "Сошедшего с ума ветра" неожиданно набрался таймер... Так что, да, новая глава прямиком из апреля 2025 вышла. Не знаю как сейчас, но в момент написания она была невероятно уморительна))) Следующая часть это стекольное БиУ, кстати 🙂
custom 53348313027324389993
#архив Ложь во благо ● Фэндом: Клуб Романтики: Водяная лилия. ● Персонажи: Деклан Романо/Райли Пирс. ● Рейтинг: PG-13. ● Направленность: Гет. ● Метки: Hurt/Comfort, Драма, Пропущенная сцена, Романтика, Согласование с каноном, Воспоминания, Развитие отношений. ● Описание: Деклан Романо всегда умел вывести Райли из себя. Тогда, много лет назад, уезжая из города, она думала, что больше никогда не переступит порог нека…
custom 53346598777027553192
Природа настолько очистилась, что вышла новая часть статей... С ума сойти...
📖 "Как написать фанфик и не сесть в лужу?" : new Написание. 7 базовых сюжетов Кристофера Букера
❤🔥3
Теория прикрытия » 21. И грянуло самое страшное
custom 53346598777027553192
ㅤПодловила красивое у "Сошедшего с ума ветра". Давайте ещё 300 тысяч, чтобы вообще красота была) Кстати, у меня цифра 4 ассоциируется с проблемой четырёх красок, когда любую карту можно раскрасить четырьмя цветами и при этом все соседние страны будут разного цвета. Так сказать, познавательная минутка!
🤩7
ㅤУ "Гейм, сет, матч, Аверрис" был бюджет из просмотра восьми серий "Первой ракетки" на Винке, двухчасовой игры в настольный теннис, 0,5 Хеллеса и 3 поисковых запросов... А! И первой версии обложки, где припадочная нейросетка сделала Сайлену дополнительный палец для более успешной игры в теннис. Короче говоря, это определённо стоит вашего внимания 🤲 Приятного чтения!
❤🔥2
ㅤА что если... AU × БиУ, где она борется за дом своих родителей, а он помогает ей в этой неравной борьбе. Олеся села на краешек стула, положила бумаги на стол и выпалила, потому что иначе просто не смогла бы начать: — Наш берег собираются застроить! У вас, как я понимаю, единственный участок, который еще не продан! Мой дом я тоже пока не продала! Так что нас тут только двое тех, кто не согласился на их условия… — …
❤🔥8💔3
ㅤ Кто бы знал, что с электронной книжки так удобно вычитывать свою же писанину... Взяла себе заслуженный отпуск и лениво пописываю всё и сразу, потому что больше ни о чём думать не надо. Как говорится: жить хорошо, а хорошо жить - ещё лучше!
😍7
— Думаете, я поверю вам? Вашему обещанию? — усмехнулся Дима. — Дмитрий, ценой вашего недоверия может стать жизнь! — перебив его, Хольт махнул ладонью, в которой сжимал пистолет. — Возможно. Это лучше, чем поверить вам, — Дима вернул себе самообладание и скрестил руки на груди. Хольт вздрогнул, как если бы его окатили ведром ледяной воды, а не парой прохладных фраз. #цитата из "Поймать абонента"
🔥3
ㅤУ меня нет абсолютно никаких объяснений тому, как получилась "Ложь во благо" по "Водяной лилии". Нет, чисто техническое объяснение, конечно, есть: с месяц примерно пылились в заметках две разрозненные сцены обоюдных нападок Райли и Деклана, но пока я шлифовала их, никак не могла понять, что может их связать воедино. И слепилось всё... глиной. Причём буквально, потому что на днях мне пришлось посмотреть с десяток тут…
😍4
Showing the 12 most recent of 20 posts we hold for @katecoronadowrite. 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 — 1,033,791 of 1,336,469entries 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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Катя (Вера) пишет...” (@katecoronadowrite), 94 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/katecoronadowrite.
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.