Channel
@grinya_cos
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
170subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001591443424 |
|---|---|
| Type | Channel |
| Username | @grinya_cos |
| Created | 17 May 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/grinya_cos |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 06:43 | 170 | +2 |
| 23 Aug 2026, 04:47 | 168 | -2 |
| 8 Aug 2026, 15:01 | 170 | no change |
| 7 Aug 2026, 19:51 | 170 | first reading |
10 posts held, back to 10 June 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
160 reactions across 10 posts, in 12 distinct kinds. The most used accounts for 19.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍓 | 31 | 19.4% | |
| ❤🔥 | 27 | 16.9% | |
| ❤ | 22 | 13.8% | |
| custom 5262735668169155504 | 19 | 11.9% | |
| custom 5359458464819087948 | 16 | 10.0% | |
| custom 5359382366588537438 | 12 | 7.50% | |
| 💋 | 10 | 6.25% | |
| 💘 | 9 | 5.63% | |
| 🏆 | 7 | 4.38% | |
| custom 5238081001111953247 | 4 | 2.50% | |
| 🎉 | 2 | 1.25% | |
| 🔥 | 1 | 0.625% |
Custom emoji. 4 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 10 of the 10 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 160 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 10 June 2026 to 24 July 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.
🔡🔡🔡🔡0️⃣🔡📜📜📜📜📜📜📜 🤍𝐀𝐧𝐢𝐤𝐨𝐧 𝟐𝟎𝟐𝟔🤍 И так. Вашему вниманию наше дефиле с очаровательным Шадоу Милком 🤩 Спасибо за то, что согласилась воплотить со мной мой гиперфикс пейринг. Безмерно люблю, my dear blue bird
custom 52627356681691555046custom 52380810011119532474❤🔥3🍓2💋1custom 53593823665885374381custom 53594584648190879481
Первое место гейм дефиле. Мы кто?
🍓11🏆7custom 52627356681691555047custom 53594584648190879483🔥1
Video message, posted without a caption
❤5💋5❤🔥3🍓2custom 53594584648190879482custom 52627356681691555041
Уже сегодня выступаем в третьем блоке в групповом гейм дефиле на Аниконе
❤4🍓4custom 53594584648190879482
🤨🖖🤙 Поездка в Выборг летом 👹😩🧏♀️ уже как каноничное событие. А вообще день порадовал и погодой, и компанией 🤗
❤8❤🔥5custom 53593823665885374385💋2custom 53594584648190879481
👒👒👒 Наша заявочка с 👒👒прекрасной голубой 👒 птичкой прошла. Так что что-то типо ждите на анике 🤩 Буду подметать весь фест плащом
custom 52627356681691555045❤🔥3🍓2🎉2💋1custom 53594584648190879481
👒👒 Уже скоро дедлайн. 👒👒 Так что покажу то, 👒 что делаю. К сожалению не имею привычки фоткать процессы, поэтому только так 👀 Кто понял на кого это и откуда большие молодцы 🤎
❤🔥4🍓3custom 53593823665885374383custom 53594584648190879482
Как сказать, что вы с париком надолго? Спустя 7 лет я решила дослушать небожителей
❤🔥2custom 53594584648190879482❤1custom 53593823665885374381
Сегодня я не смогла остаться равнодушной перед пионами у какой-то милой женщины у метро. Да и ваза кофейник давно не видел цветочков 🤎
💘6🍓4❤3
👒👒 У меня просто 👒👒 всё хорошо
❤🔥7🍓3💘3custom 53593823665885374382custom 53594584648190879482❤1💋1
Showing the 10 most recent of 10 posts we hold for @grinya_cos. 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Гринечка” (@grinya_cos), 170 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/grinya_cos.
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.