Артик за первое место @Suuunnnnnnnnnnn
custom 54271354842728531347
Signed Рин Корогамэ

Channel
@Rin_koro
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
200subscribers
-6 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001552186827 |
|---|---|
| Type | Channel |
| Username | @Rin_koro |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/Rin_koro |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 03:38 | 200 | -1 |
| 9 Sept 2026, 09:15 | 201 | -1 |
| 25 Aug 2026, 04:16 | 202 | -3 |
| 17 Aug 2026, 13:33 | 205 | -1 |
| 10 Aug 2026, 15:30 | 206 | no change |
| 10 Aug 2026, 15:17 | 206 | first reading |
12 posts held, back to 3 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
126 reactions across 12 posts, in 9 distinct kinds. The most used accounts for 28.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5310033170882650644 | 36 | 28.6% | |
| custom 5427135484272853134 | 35 | 27.8% | |
| ❤ | 27 | 21.4% | |
| 🔥 | 9 | 7.14% | |
| custom 5278389694386706091 | 7 | 5.56% | |
| ❤🔥 | 5 | 3.97% | |
| custom 5255888459507197659 | 3 | 2.38% | |
| custom 5256195055747619967 | 2 | 1.59% | |
| 🍓 | 2 | 1.59% |
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 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 12 of the 12 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 126 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 3 August 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.
Артик за первое место @Suuunnnnnnnnnnn
custom 54271354842728531347
Signed Рин Корогамэ
Остановите меня #Валентин #Марк #Терренс
❤4custom 53100331708826506444
Signed Рин Корогамэ
Бля держите меня семеро😆
❤1
Signed Рин Корогамэ
Ммм гиперфиксы классная штука Забавный факт что это изначально не планировалось как косплей Вали на Эла, но в процессе оно само....
custom 542713548427285313411custom 52558884595071976593custom 53100331708826506443
Signed Рин Корогамэ
Скетчик с Рин сам нарисовался #Рината #РусРеал
custom 542713548427285313412custom 52783896943867060913🍓2custom 52561950557476199672
Signed Рин Корогамэ
Немного переставил штуки 🤩 В надежде что так будет удобней 😳 #Щитпост
custom 531003317088265064411❤2
Signed Рин Корогамэ
🤩С днем рождения меня🤩 Лучший подарок художнице это репост и все такое. Мне очень нравится большая часть картинок за этот год, надеюсь, что смогу продолжать в том же духе 🍪 Всем спасибо, что вы тут со мной, смотрите на мои картинки и ОСов🦕
❤4
Signed Рин Корогамэ
Рьюзаки он тут получился как ребёнок, но изначально это не входило в план Он тут как в аниме должен был быть🥲 #ТетрадьСмерти
custom 53100331708826506447❤3custom 52783896943867060911
Signed Рин Корогамэ
Утречка, я слишком люблю тетрадку😍🥺 Я люблю и Лайта и Рьюзаки, но любовь разная Если 😀🌷🤪😊 мне нравится как еблан антагонист, типа выебать и въебать! То 🔠 обнять и плакать😭
custom 54271354842728531345
Signed Рин Корогамэ
Комп обманывает меня в цветах
🔥5custom 53100331708826506443custom 52783896943867060911
Signed Рин Корогамэ
Второе место готово @sorka_m
custom 53100331708826506445❤4🔥4❤🔥3custom 52783896943867060911
Signed Рин Корогамэ
Фан-арты Миса такая лапочка🥰
❤9custom 53100331708826506443❤🔥2custom 52783896943867060911
Signed Рин Корогамэ
Showing the 12 most recent of 12 posts we hold for @Rin_koro. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Rin.Koro_😈” (@Rin_koro), 200 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Rin_koro.
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.