Sticker, posted without a caption

Channel
три дня романтики
@Rikya666
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
309subscribers
+58 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003963128995 |
|---|---|
| Type | Channel |
| Username | @Rikya666 |
| Created | Between 1 April 2026 and 28 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Rikya666 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 13:07 | 309 | +58 |
| 7 Aug 2026, 02:18 | 251 | no change |
| 6 Aug 2026, 21:46 | 251 | first reading |
Engagement
12 posts held, back to 28 July 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 · 30 days
- 67.4%
- avg views ÷ 309 subscribers
- Avg views / post
- 208
- 12 posts measured
- Reaction rate
- 17.6%
- reactions ÷ views · ER floor
- Posts in window
- 12
- of 12 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. It is computed over the 8 of 12 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 12 (28 July 2026 – 6 August 2026) |
| Views total | 2,498 |
| Reactions total | 354 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 02:18 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
354 reactions across 8 posts, in 18 distinct kinds. The most used accounts for 16.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5310298544026984209 | 57 | 16.1% | |
| custom 5431411721216498819 | 41 | 11.6% | |
| custom 5431776527148689414 | 35 | 9.89% | |
| custom 5431437460955503044 | 33 | 9.32% | |
| custom 5467394020919499448 | 32 | 9.04% | |
| custom 5433785858878644617 | 29 | 8.19% | |
| custom 5231400935397298794 | 21 | 5.93% | |
| custom 5431718386176404695 | 21 | 5.93% | |
| custom 5431679057160872667 | 19 | 5.37% | |
| custom 5357385786616486188 | 16 | 4.52% | |
| custom 5298626373399650570 | 13 | 3.67% | |
| custom 5312527881161712925 | 12 | 3.39% | |
| custom 5312175238576909035 | 10 | 2.82% | |
| custom 5404339855155035899 | 7 | 1.98% | |
| custom 5228988211748969443 | 3 | 0.847% | |
| custom 5215407825806730169 | 2 | 0.565% | |
| custom 5433634787698975107 | 2 | 0.565% | |
| custom 5310264089799335199 | 1 | 0.282% |
Custom emoji. Every row above is a 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 8 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 354reactions 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 28 July 2026 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.
Recent posts
рк / мью рп
🖤🖤🖤🖤🖤 🖤🖤🖤 💭Прогулка по ночному Парижу💭🤩🤩 🤩сюжет 1🤩сюжет 2🖤 🌟🌟🤩🤩🤩🤩 🌟🌟tag$: #CMH 🤩🤩 🤩 - отсосать 🌟🌟🌟 🤩 - потрогать сисю 🤩🤩⭐🔤🔤+ рк = new 🤩🤩pо$t⭐ boost🔤mew post🔤anon —@anonRikya666bot 🤩
custom 54317183861764046955custom 54314374609555030443custom 54317765271486894143custom 53573857866164861882custom 54314117212164988191custom 54316790571608726671
🖤🖤🖤🖤🖤 🖤🖤🖤 💭Курение с кровью💭🤩🤩 🤩сюжет 1🤩сюжет 2🖤 🌟🌟🤩🤩🤩🤩 🌟🌟tag$: #CMH 🤩🤩 🤩 - отсосать 🌟🌟🌟 🤩 - потрогать сисю 🤩🤩⭐🔤🔤+ рк = new 🤩🤩pо$t⭐ boost🔤mew post🔤anon —@anonRikya666bot 🤩
custom 543141172121649881927custom 543143746095550304412custom 543167905716087266711custom 54317765271486894145custom 53573857866164861881custom 54317183861764046951custom 54336347876989751071custom 54337858588786446171
Sticker, posted without a caption
🖤🖤🖤🖤🖤 🖤🖤🖤 💭Разбитая машина 18+💭🤩🤩 🤩сюжет 1🤩сюжет 2🖤 🌟🌟🤩🤩🤩🤩 🌟🌟tag$: #CMH 🤩🤩 🤩 - отсосать 🌟🌟🌟 🤩 - потрогать сисю 🤩🤩⭐🔤🔤+ рк = new 🤩🤩pо$t⭐ boost🔤mew post🔤anon —@anonRikya666bot 🤩
custom 543378585887864461728custom 543171838617640469513custom 535738578661648618811custom 54314374609555030446custom 54316790571608726672custom 54317765271486894142custom 52154078258067301691custom 54336347876989751071
🖤🖤🖤🖤🖤 🖤🖤🖤 💭Наркодилер💭🤩🤩 🤩сюжет 1🤩сюжет 2🖤 🌟🌟🤩🤩🤩🤩 🌟🌟tag$: #CMH 🤩🤩 🤩 - отсосать 🌟🌟🌟 🤩 - потрогать сисю 🤩🤩⭐🔤🔤+ рк = new 🤩🤩pо$t⭐ boost🔤mew post🔤anon —@anonRikya666bot 🤩
custom 543177652714868941425custom 543141172121649881913custom 543143746095550304412custom 54316790571608726675custom 52154078258067301691
🖤🖤🖤🖤🖤 🖤🖤🖤 💭Стань моим продюсером💭🤩🤩 🤩сюжет 1🤩сюжет 2🖤 🌟🌟🤩🤩🤩🤩 🌟🌟tag$: #CMH 🤩🤩 🤩 - отсосать 🌟🌟🌟 🤩 - потрогать сисю 🤩🤩⭐🔤🔤+ рк = new 🤩🤩pо$t⭐ boost🔤mew post🔤anon —@anonRikya666bot 🤩
custom 531029854402698420927custom 546739402091949944814custom 531252788116171292512custom 53121752385769090355custom 54317183861764046952custom 52289882117489694431custom 52314009353972987941custom 53102640897993351991
File, posted without a caption
custom 53121752385769090354
Покажи себя такой, чтоб не выйти из башки🤩 🔆 приму тебя любой, будто дж4нки пор0шки🤩 Гулом сотен городов передам тебе привет🤩🤩🔤🔤🔤🔤 это не любовь значит бога больше нет🤩
custom 531029854402698420916custom 529862637339965057010custom 54043398551550358997custom 53573857866164861882custom 54673940209194994482custom 52289882117489694431
Sticker, posted without a caption
🖤🖤🖤🖤🖤 🖤🖤🖤 💭Резиновые уточки💭🤩🤩 🤩сюжет 1🤩сюжет 2🖤 🌟🌟🤩🤩🤩🤩 🌟🌟tag$: #CMH 🤩🤩 🤩 - отсосать 🌟🌟🌟 🤩 - потрогать сисю 🤩🤩⭐🔤🔤+ рк = new 🤩🤩pо$t⭐ boost🔤mew post🔤anon —@anonRikya666bot 🤩
custom 523140093539729879420custom 546739402091949944816custom 531029854402698420914custom 52986263733996505703custom 52289882117489694431custom 53121752385769090351
Showing the 12 most recent of 12 posts we hold for @Rikya666. 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 — 137,938 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
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.
Mentions
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“три дня романтики” (@Rikya666), 309 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Rikya666.
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.