Channel
@gyuvu
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
51subscribers
+11 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003066958027 |
|---|---|
| Type | Channel |
| Username | @gyuvu |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/gyuvu |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 01:57 | 51 | +2 |
| 30 Aug 2026, 21:36 | 49 | +3 |
| 23 Aug 2026, 11:03 | 46 | +2 |
| 16 Aug 2026, 04:27 | 44 | +3 |
| 10 Aug 2026, 18:01 | 41 | no change |
| 9 Aug 2026, 14:21 | 41 | +1 |
| 9 Aug 2026, 08:32 | 40 | first reading |
11 posts held, back to 21 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 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 11 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
175 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 22.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5255735017505589557 | 40 | 22.9% | |
| custom 5318892803651046034 | 38 | 21.7% | |
| custom 5321155998012967381 | 27 | 15.4% | |
| custom 5193054612680111249 | 24 | 13.7% | |
| custom 5262802326061618680 | 20 | 11.4% | |
| custom 5395596787799069000 | 14 | 8.00% | |
| custom 5346159815846562441 | 8 | 4.57% | |
| custom 5368817142722498374 | 4 | 2.29% |
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 11 of the 11 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 175 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 21 July 2026 to 7 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.
Posted without readable text
custom 51930546126801112495custom 52557350175055895574custom 53955967877990690003custom 53188928036510460342custom 52628023260616186801custom 53211559980129673811
Signed 모방 | Giyuu Deøs #PiersFAN
Posted without readable text
custom 51930546126801112494custom 53188928036510460343custom 53955967877990690003custom 52557350175055895571custom 52628023260616186801custom 53211559980129673811custom 53461598158465624411custom 53688171427224983741
Signed 모방 | Giyuu Deøs #PiersFAN
Всем привет!! Артфайт подошел к концу, так что показываю вам подборку работ, что мне понравились Спасибо всем большое за вашу поддержку и отдачу. Спасибо всем, кто мотивировал меня атаковать всех и так же, благодарю тех, кто атаковал меня. Если кого-то из вас я не успел ревенжнуть то постараюсь исправиться в следующем году. Хоть это и был мой второй раз, он вышел очень ярким, за этот месяц я сделал 7 анимированных …
custom 52557350175055895577custom 53188928036510460345custom 52628023260616186804custom 51930546126801112492custom 53211559980129673811custom 53688171427224983741custom 53955967877990690001
Signed 모방 | Giyuu Deøs #PiersFAN
Photo, posted without a caption
custom 53188928036510460344custom 51930546126801112492custom 53211559980129673812custom 52557350175055895571custom 52628023260616186801custom 53955967877990690001
Signed 모방 | Giyuu Deøs #PiersFAN
Я ГОРЖУСЬ И ИСКРЕННЕ ПОЛЬЩЕНА МУКА НАЦИЯ ВПЕРЕЕЕЕД
custom 53211559980129673814custom 53188928036510460343custom 52557350175055895572custom 51930546126801112491custom 52628023260616186801custom 53955967877990690001
Signed 모방 | Giyuu Deøs #PiersFAN
трейд трейд треййййд🥺
custom 53211559980129673814custom 51930546126801112493custom 52557350175055895573custom 53188928036510460341
Signed 모방 | Giyuu Deøs #PiersFAN
Всем привет заскочил в последний вагон артфайта чтобы сделать ревенж шприцу 👀 Попозже подведу итоги артф
custom 52557350175055895575custom 53188928036510460344custom 52628023260616186803custom 51930546126801112492custom 53211559980129673811custom 53955967877990690001
Signed 모방 | Giyuu Deøs #PiersFAN
Трейд с @.flinsbedo 😆 кайф, я бы завел еще один монолог как люблю чужие юмешипы/селфшипы, ноо это попозже🤫
custom 53188928036510460347custom 52628023260616186806custom 52557350175055895575custom 53688171427224983741custom 53955967877990690001
Signed 모방 | Giyuu Deøs #PiersFAN
две крутых атаки🙈
custom 52557350175055895575custom 53211559980129673815custom 51930546126801112494custom 52628023260616186801custom 53188928036510460341custom 53688171427224983741custom 53955967877990690001
Signed 모방 | Giyuu Deøs #PiersFAN
анимационная атака митч и лиф🤔
custom 52557350175055895576custom 53188928036510460344custom 53211559980129673814custom 51930546126801112491custom 52628023260616186801custom 53955967877990690001
Signed 모방 | Giyuu Deøs #PiersFAN
атаки
custom 53461598158465624417custom 53188928036510460344custom 53211559980129673814custom 52557350175055895571custom 52628023260616186801custom 53955967877990690001
Signed 모방 | Giyuu Deøs #PiersFAN
Showing the 11 most recent of 11 posts we hold for @gyuvu. 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.
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 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Прошлое вчера” (@gyuvu), 51 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/gyuvu.
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.