рест 🥺
custom 535053234166199525513custom 53508010477009412424custom 53508087528722673763

Channel
@shrk0809
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
198subscribers
+7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004478375406 |
|---|---|
| Type | Channel |
| Username | @shrk0809 |
| Created | Between 1 June 2026 and 2 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/shrk0809 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 04:17 | 198 | +1 |
| 20 Aug 2026, 11:43 | 197 | +5 |
| 14 Aug 2026, 10:39 | 192 | +1 |
| 7 Aug 2026, 07:15 | 191 | no change |
| 6 Aug 2026, 22:02 | 191 | first reading |
17 posts held, back to 2 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 17 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
488 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 36.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5350801047700941242 | 180 | 36.9% | |
| custom 5350532341661995255 | 161 | 33.0% | |
| custom 5350808752872267376 | 147 | 30.1% |
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 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 16 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 488 reactions 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 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.
рест 🥺
custom 535053234166199525513custom 53508010477009412424custom 53508087528722673763
!!!!!!!
custom 53508087528722673769
✶ / / t.me/weeknd_lover aka the most hardworking man on earth 💱 #evan_lee
!!!!!!!!
custom 535080875287226737610
‼️ ребят, пожалуйста, срочно зайдите в тви и заблокируйте пользователя @/BlackMajiks! этот аккаунт сейчас активно распространяет жестокий хейт в сторону ни-ки. давайте защитим нишимуру от хейтеров и коллективно кинем репорты с блоками!
custom 535080875287226737613custom 53508010477009412428custom 53505323416619952555
сонхун немного перепутал машины и уже собирался ехать с чонвоном, но рики позвал его к себе, и тот сразу же пришел 🫂
custom 535053234166199525522custom 535080104770094124211custom 53508087528722673768
сонхун так мило оглядывается по сторонам, пытаясь понять, над чем это рики с джейком так смеются 😆 и ровно в тот момент, когда он встречается взглядом с ни-ки, сам расплывается в улыбке! ну что за лапочка 🤏
custom 535080104770094124216custom 535080875287226737610custom 53505323416619952556
my smiley hoonki <3
custom 535080104770094124219custom 535080875287226737610custom 53505323416619952559
ミ rk’s ‧ wvrs ‧ 8月3日 ( 🤩 ) : 🇺🇸🖤🔥🔥🔥🔥🔥🔥 ( 🤩 ) : love you guys 🇺🇸
custom 535080104770094124214custom 535053234166199525510custom 53508087528722673766
my lovely fairies 🧚🏻♂️🩷
custom 535080104770094124216custom 535053234166199525510custom 53508087528722673769
sh’s ‧ wvrs DM ‧ 8월3일 ( 🤩 ) : тур по северной и южной америке прошёл так весело, хе-хе. мы пробыли там действительно довольно долго ( 🤩 ) : думаю, это станет ещё одним потрясающим воспоминанием. точно, дальше у нас пусан! файтин! ( 🤩 ) : а вы уже ходили купаться? погода сейчас должна быть в самый раз ( 🤩 ) : я слышал, в корее сейчас тоже стоит сильная жара, так что будьте осторожны, чтобы не получить тепловой уда…
custom 535053234166199525510custom 535080104770094124210custom 53508087528722673767
🧍🧍🧍
custom 535080104770094124215custom 535053234166199525510custom 53508087528722673769
Showing the 12 most recent of 17 posts we hold for @shrk0809. 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 22 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“deux dates, un destin ⁰⁸⁰⁹” (@shrk0809), 198 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/shrk0809.
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.