Telegram RegisterThe public register of Telegram

Channel

Ruikasa confession

@ruikasconf

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

764subscribers

+3 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002451626370
TypeChannel
Username@ruikasconf
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/ruikasconf

Growth

761764762.510 Aug 2026, 18:16 — 761 subscribers11 Aug 2026, 17:14 — 764 subscribers10 Aug 2026, 18:1611 Aug 2026, 17:14
2 measurements taken within a single day, net +3. 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 761–764 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 17:14764+3
10 Aug 2026, 18:16761first reading

Engagement

17 posts held, back to 2 August 2026the 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 · 30 days
25.8%
avg views ÷ 764 subscribers
Avg views / post
197
17 posts measured
Reaction rate
16.0%
reactions ÷ views · ER floor
Posts in window
17
of 17 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
WindowRolling 30 days · latest post in window 10 August 2026
Posts held17 (2 August 202610 August 2026)
Views total3,355
Reactions total536
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 18:16 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.

Reaction mix

536 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 29.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 541348148688613026515829.5%
custom 541611285013963292012623.5%
custom 507573412354116928810219.0%
💘448.21%
336.16%
❤‍🔥325.97%
🍓275.04%
😢61.12%
🔥30.56%
💋20.373%
🎉10.187%
💔10.187%
🕊10.187%

Custom emoji. 3 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 17 of the 17 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 536reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 2 August 2026 to 10 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.

Recent posts

10 Aug 2026, 18:08 UTC38 views10 reactionsread 10 August 2026
Photo

тгк @okunyokku #тейк : @rkstakebot 𖹭 🎈🌟

custom 50757341235411692885custom 54161128501396329203custom 54134814868861302652

10 Aug 2026, 18:08 UTC38 views4 reactionsread 10 August 2026
Photo

АРТ НЕ МОЙ, CR. @miru_crepe в твиттере!! Или х я не знаю как он называется! Ребзи. Я недавно начал стараться разобраться в аушках по руикасам, и мне стало интересно откуда взялась эта ау? Есть ли карты от которых она произошла? Как она называется? ПОЧЕМУ ТУТ ЦУКАСА ПОСТОЯННО С ЧУПИКОМ? #тейк : @rkstakebot 𖹭 🎈🌟

custom 50757341235411692884

10 Aug 2026, 13:51 UTC114 views30 reactionsread 10 August 2026
Photo

я люблю джестера, вы любите джестера, мы любим джестера ❤️❤️❤️ тгк: @ayashatsukasakinn #тейк : @rkstakebot 𖹭 🎈🌟

13custom 54134814868861302657💘4custom 50757341235411692882custom 54161128501396329202❤‍🔥1🔥1

10 Aug 2026, 12:25 UTC132 views22 reactionsread 10 August 2026
Photo

Сорсевальчики любимые ⚔️🔮🔮 Работа на дтис!! тгк @tayoshha_art #тейк : @rkstakebot 𖹭 🎈🌟

12custom 54134814868861302655custom 54161128501396329204custom 50757341235411692881

9 Aug 2026, 10:54 UTC163 views26 reactionsread 10 August 2026
Photo

каса7 не отпускает сос тгк @sigmyashka11 #тейк : @rkstakebot 𖹭 🎈🌟

❤‍🔥14🍓5💘4custom 54134814868861302652custom 54161128501396329201

9 Aug 2026, 10:54 UTC168 views27 reactionsread 10 August 2026
Photo

@krevetkakamiii тг #тейк : @rkstakebot 𖹭 🎈🌟

custom 541611285013963292016💘6🍓3custom 54134814868861302652

9 Aug 2026, 09:20 UTC181 views42 reactionsread 10 August 2026
Photo

"my middle school self" тгк @jul1zzz #тейк : @rkstakebot 𖹭 🎈🌟

❤‍🔥16custom 541348148688613026512custom 50757341235411692887custom 54161128501396329203💘21🕊1

8 Aug 2026, 07:29 UTC199 views54 reactionsread 10 August 2026
Photo

сарсевале плюшки мчатся ко мне с Китая. они настолько крутые, что им устроили маленькую фотосессию на китайском складе. они такие безмозглые ⚔️🔮 #тейк : @rkstakebot 𖹭 🎈🌟

custom 541348148688613026532custom 541611285013963292011custom 507573412354116928862❤‍🔥1🍓1💘1

7 Aug 2026, 14:03 UTC208 views55 reactionsread 10 August 2026
Photo

аьсьыбчдлхху, тсукаса гонщик и руи механик ❤️❤️❤️ @ayashatsukasakinn - 🏎 @nik0tiiiin - 🔧 #тейк : @rkstakebot 𖹭 🎈🌟

custom 541348148688613026530custom 507573412354116928812custom 541611285013963292010💘2🍓1

7 Aug 2026, 08:22 UTC215 views37 reactionsread 10 August 2026
Photo

руи обнимашки плбш касу тв голенький руи… МНЕ НЕ ОХОТО БЫЛО ДЕЛАТЬ ОДЕЖДУ… тгк @kamishiroririi #тейк : @rkstakebot 𖹭 🎈🌟

custom 541611285013963292023😢6custom 54134814868861302654🔥2custom 50757341235411692882

6 Aug 2026, 16:15 UTC224 views28 reactionsread 10 August 2026
Photo

тсюкася кун спит тгк @norimsi69 #тейк : @rkstakebot 𖹭 🎈🌟

custom 507573412354116928818custom 54134814868861302656custom 54161128501396329204

6 Aug 2026, 14:19 UTC221 views45 reactionsread 10 August 2026
Photo

тгк @ren_st4r #тейк : @rkstakebot 𖹭 🎈🌟

custom 541348148688613026522custom 541611285013963292014custom 50757341235411692889

Showing the 12 most recent of 17 posts we hold for @ruikasconf. 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

Citation-graph rank — 118,035 of 1,340,412entries 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.

Forward network

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.

Mentions

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Ruikasa confession” (@ruikasconf), 764 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ruikasconf.

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.