Telegram RegisterThe public register of Telegram
Telegram profile photo for Liss

Channel

Liss

@ricynky_riny

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

398subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002410579923
TypeChannel
Username@ricynky_riny
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/ricynky_riny

Growth

398399398.57 August 2026 — 398 subscribers8 August 2026 — 398 subscribers8 August 2026 — 399 subscribers16 August 2026 — 398 subscribers7 August 202616 August 2026
4 measurements spanning 9 days. 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 398–399 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 16:08398-1
8 Aug 2026, 08:32399+1
8 Aug 2026, 05:49398no change
7 Aug 2026, 16:50398first reading

Engagement

19 posts held, back to 12 November 2025the 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
98.2%
avg views ÷ 398 subscribers
Avg views / post
391
5 posts measured
Reaction rate
11.2%
reactions ÷ views · ER floor
Posts in window
5
of 19 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 6 August 2026
Posts held19 (12 November 20256 August 2026)
Views total1,955
Reactions total218
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05:49 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.

What this channel posts

Video runtime
1s
Average length
1s

Measured directly from 1 video 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.

Reaction mix

1,557 reactions across 19 posts, in 25 distinct kinds. The most used accounts for 34.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 536208107922418036353134.1%
custom 544986009181148217430519.6%
custom 545878036092814096521113.6%
1157.39%
custom 5393570379279113181855.46%
custom 5386506081495166328543.47%
🍓432.76%
❤‍🔥342.18%
💘332.12%
custom 5256072507445777033311.99%
custom 5341429493485574514191.22%
🎉191.22%
custom 5267089721330253463140.899%
custom 5334708591221840755140.899%
custom 5902268633689627367110.706%
custom 6034845731427191885110.706%
custom 603501492736885092170.45%
custom 538878718587071053840.257%
custom 547225018582225988930.193%
custom 603491508655908825830.193%
5 further kinds100.642%

Custom emoji. 15 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 19 of the 19 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 1,557reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 12 November 2025 to 6 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.

Telegram Stars

Stars received
115
across the posts below
Posts paid on
13
of 19 we hold a reading for · 68%
Most on one post
57
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ricynky_riny. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 19 most recent posts we hold for this entry, published 12 November 2025 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Aug 2026, 17:19 UTC87 views22 reactionsread 8 August 2026

Какой у вас любимый персонаж/пейринг из крипипасты? Кого нарисоватт ещё

custom 525607250744577703310custom 526708972133025346365custom 54498600918114821741

6 Aug 2026, 14:30 UTC320 views46 reactionsread 8 August 2026
Photo

Скоро слезу с тяжёлых 1/9

custom 544986009181148217423custom 538650608149516632813custom 525607250744577703391

3 Aug 2026, 15:19 UTC429 views58 reactionsread 8 August 2026
Photo

Приплюснутый

34custom 525607250744577703312custom 52670897213302534638custom 53865060814951663283custom 54498600918114821741

27 Jul 2026, 12:28 UTC334 views29 reactionsread 8 August 2026
Poll

Хочу узнать возраст основной аудитории, выберите свой диапазон пожалуйста

  1. Меньше 121%
  2. 12-1639%
  3. 17-2152%
  4. Больше 229%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

custom 534142949348557451418custom 53347085912218407554custom 60350149273688509214custom 53865060814951663283

19 Jul 2026, 17:00 UTC785 views63 reactions5 Starsread 8 August 2026
Photo

Коллаб с прекрасным художником и аниматором Hitsy!!! Решили нарисовать наших персонажей в одежде главных героев аниме "Ангел кровопролития". Иронично, что мой эмо бой в одежде Зака похож на самого Зака 😱 Быстро все идём подписываться на художницу!!! Она проделала большую часть работы над ним и получилось шикарно

custom 53865060814951663283514custom 533470859122184075510custom 60350149273688509213custom 53414294934855745141

10 Jun 2026, 17:05 UTC≈2,000 views86 reactions2 Starsread 8 August 2026
Photo

Yaoi 🐱

custom 544986009181148217450🎉19🍓12custom 545878036092814096521custom 53620810792241803631custom 59022686336896273671

5 Jun 2026, 18:56 UTC968 views68 reactionsread 8 August 2026
Video

Пробую алайт моушен 🐈‍⬛ Поздравляю с началом лета!!! Через 3 дня закрываю коммишечки, кто хотел заказать, пишем пишем!

custom 545878036092814096534custom 536208107922418036320custom 590226863368962736710custom 53866040153394508312custom 54498600918114821742

9 May 2026, 16:01 UTC≈1,600 views64 reactionsread 8 August 2026
Photo

Всем привет

custom 536208107922418036338custom 544986009181148217414custom 54587803609281409657❤‍🔥2custom 538878718587071053821

24 Apr 2026, 15:30 UTC≈2,170 views85 reactions3 Starsread 8 August 2026
Photo

Трейд с @RAX404TTTTT наконец-то ааа 🤩 А ещё новый покрасек волос

custom 545878036092814096544custom 536208107922418036318🍓13custom 544986009181148217442❤‍🔥2custom 53887871858707105382

31 Mar 2026, 16:28 UTC≈2,130 views83 reactions3 Starsread 8 August 2026
Photo

Первая есть ☺️ Ну что вы как там, все живы?

custom 536208107922418036346custom 545878036092814096518custom 5449860091811482174124❤‍🔥1🍓1custom 54723211429769519731

5 Mar 2026, 15:01 UTC≈1,520 views99 reactions2 Starsread 8 August 2026
Photo

Коллаб но не говорим кого рисуем с прекрасной @hornyuvu !!! 😡 Максимально странно, но мне очень понравилось

custom 53935703792791131814928custom 544986009181148217415custom 53620810792241803634custom 60349150865590882582custom 54587803609281409651

14 Feb 2026, 12:36 UTC≈1,460 views102 reactions14 Starsread 8 August 2026
Photo

💖 Поздравляю с 14 февраля!!! 💖 Очень надеюсь, что этот день вы проведёте с хорошим настроением и не будете скучать Артик старый, но как по мне достаточно подходящий ❤️

custom 536208107922418036355❤‍🔥23custom 544986009181148217416💘62

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

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.

27 Jul 2026, 12:28 UTCAnonymous Poll132 voters

Хочу узнать возраст основной аудитории, выберите свой диапазон пожалуйста

  1. Меньше 121%
  2. 12-1639%
  3. 17-2152%
  4. Больше 229%

Shares as published, totalling 101%. 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 19 most recent posts we hold, published 12 November 2025 to 6 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.

Citation-graph rank

Citation-graph rank — 904,494 of 1,480,975entries 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.

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

“Liss” (@ricynky_riny), 398 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/ricynky_riny.

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.