Channel
@guyugaga
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
79subscribers
+10 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002179941280 |
|---|---|
| Type | Channel |
| Username | @guyugaga |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/guyugaga |
Gaming — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 |
|---|---|---|
| 8 Oct 2026, 17:20 | 79 | +1 |
| 29 Sept 2026, 07:36 | 78 | +4 |
| 14 Sept 2026, 08:57 | 74 | +3 |
| 6 Sept 2026, 22:58 | 71 | -1 |
| 30 Aug 2026, 00:26 | 72 | +3 |
| 14 Aug 2026, 19:16 | 69 | no change |
| 14 Aug 2026, 19:05 | 69 | first reading |
17 posts held, back to 16 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 17 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.
67 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 37.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍓 | 25 | 37.3% | |
| 🔥 | 24 | 35.8% | |
| ❤🔥 | 18 | 26.9% |
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 67 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 16 July 2026 to 13 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.
Так-так, важное заявление, в воскресенье наконец-то залью ролик на ютуб с первой частью адоптов, также в этом шопе: @butchers_shops, они будут продаваться с начальной ставкой даром, можете подписаться, сюда я не буду дублировать ауки, так что вы легко можете все пропустить, дублировать о ауках я буду на этот канал: @zenkoykuAUC Это, собственно, всё, что я хотела сказать, прошу во внимание взять все сказанное, хороше…
❤🔥2🍓1🔥1
СИКС НАЙН, СИКС НАЙН
🔥2🍓1
Стрим во вторник(11.08), 13:00 мск #стрим
❤🔥2
Posted without readable text
Ребят, я увидела эту проблему только сейчас и решила выставить этот пост, извиняюсь перед теми, кто уже начал рисовать, ничего вам исправлять не нужно, но те, кто еще не начал, я в коммы кину сейчас все версии файлом, чтобы вы глянули, там родинки и всякие другие детали персонажа намного лучше🙏 #флуд
🔥5
Смотрите, как моих дочек нарисовали, я фигею, ну хот, хот Тгк худа: @grimykent
🍓5
Вечный ивент — Суть: первый кто заскринит то или иное количество подписчиков получит денежное вознаграждение 67 подписчиков — 10 рублей 100 подписчиков — 100 рублей 150 подписчиков — 150 рублей 200 подписчиков — 200 рублей 250 подписчиков — 250 рублей РФ карта или через сайты, где доступен СБП. Комиссия за перевод лежит не на мне
❤🔥4🍓1🔥1
Спасибки за стрим, сяб за коллабу с аой и эпилепсиком, сябки за коллабик с рафилодочкой, и сябки за посиделки с либертом, а еще нас 30 фоллов👏 #стрим
🔥2🍓1
Напоминалка — В 9:00 по мск, 27 июля(пн) состоится #стрим! Скорее всего на нем сначало порисую коллабу, после арт на конкурс
❤🔥2
Ребята, коллаба! Кидайте в коммы своих персонажей (можете кинуть хоть всех, но я выберу от одного человека, только одного персонажа, который понравится больше) #флуд 9/9.
🔥3🍓1
Пока рисовала смотрела видео Юниверси и похоже это отпечаталось на итоге работы😨 #флуд
🍓3
Реквест для: @blog_yura #фулл #реквест
🍓4
Showing the 12 most recent of 17 posts we hold for @guyugaga. 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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“КОНКУРСᅠᅠ{💰}𝗭ᴇnᴋᴏyᴋu” (@guyugaga), 79 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/guyugaga.
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.