-1 (
![Telegram profile photo for [РЕСТ]^|Shini косплеїть|^](https://cdn.tgregister.com/av/77/77f82c9dba9d2a7c20bc4147d584e1c4ca3faabf307a1b78cd50e1dd1876eba4.jpg)
Channel
[РЕСТ]^|Shini косплеїть|^
@shinilospley
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
71subscribers
-4 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003847157096 |
|---|---|
| Type | Channel |
| Username | @shinilospley |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/shinilospley |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 17:44 | 71 | -4 |
| 9 Aug 2026, 21:31 | 75 | no change |
| 8 Aug 2026, 14:47 | 75 | first reading |
Engagement
13 posts held, back to 4 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 58.6%
- avg views ÷ 71 subscribers
- Avg views / post
- 41.6
- 13 posts measured
- Reaction rate
- 7.33%
- reactions ÷ views · ER floor
- Posts in window
- 13
- of 13 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 4 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 13 (4 August 2026 – 9 August 2026) |
| Views total | 541 |
| Reactions total | 11 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 21:31 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
- 5s
- Average length
- 5s
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
11 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 63.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5282818136381340589 | 7 | 63.6% | |
| custom 5355251454158326342 | 2 | 18.2% | |
| custom 5364219281447862819 | 2 | 18.2% |
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 4 of the 13 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 11reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 4 August 2026 to 9 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
перука готова, ше якось навчитись лінзи вдягати
Video message, posted without a caption
custom 52828181363813405892
Які ж вони котики, я зараз заплачу! Я думала мене на хуй пошлют
custom 53552514541583263422custom 53642192814478628192
краса
custom 52828181363813405893
Любі, пропаду на кілька днів, їду в село до батьків , думаю в неділю вже буду вдома 🥺
custom 52828181363813405892
07.08 ей ей ей а у кого сегодня день рождения? 💋 Ой да это же у меня !)🕯 Сегодня мне исполняется 1️⃣9️⃣ лет🎀. Со мной празднуют мои любимые мальчики, Левон секс Кеннеди, Санджи, Чайка Стив и конечно же Seven minutes it's all i can spare to play with you👁 К сожалению все день рождения я провожу в дороге но ничего страшного!)⭐️ Хочу сказать что этот год выдался мега крутым , столько всего произошло и мои соцсети очен…
∩ ∩ (๑^◡^๑) ┏♪━・━〇━・〇・━+☆+┓ 6 до 190 ┗+☆+━・━・━ + ━・━♬┛ Рт/м'ю?
З днем народження!!!
HAPPY BIRTHDAY TO ME!! дякую всім, хто був поруч зі мною цей рік. він був дуже насиченим, складним, але неймовірно пам’ятним. я вдячна кожному, хто став частиною цього періоду мого життя, всім, хто підтримував мене, сміявся разом зі мною й просто був поруч. вдячна й тим, з ким наші шляхи розійшлися, ви теж залишили свій слід у моєму житті. окреме дякую тим, хто привітав мене заздалегідь, та відсвяткував цей день зі…
╚» Kiniters«╝ Aether: “We’re looking for answers. Can you help us?” Kinich: “If our goals align, I’ll lend you my strength.” ≪ ◦ ❖ ◦ ≫ Kinich- @Ajaxdormitory
💘- самий теплий спогад це тоді коли ми прівитали Марі з днем народження! Це було дуже крута ☺️
Showing the 12 most recent of 13 posts we hold for @shinilospley. 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 — 744,299 of 1,481,306entries 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
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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@shinilospley named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 10 August 2026 – 10 August 2026 · confirmed gone 16 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“[РЕСТ]^|Shini косплеїть|^” (@shinilospley), 71 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/shinilospley.
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.