Channel
@ADVOCAA_t
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003582887628 |
|---|---|
| Type | Channel |
| Username | @ADVOCAA_t |
| Created | Between 1 December 2025 and 18 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 4 times, most recently 10 September 2026 |
| On Telegram | t.me/ADVOCAA_t |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 02:57 | 9 | no change |
| 14 Aug 2026, 12:16 | 9 | first reading |
17 posts held, back to 18 April 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 28 July 2026. An engagement rate over an empty window would be a number about nothing.
66 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 22.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5368806869160708312 | 15 | 22.7% | |
| custom 5427290021491151861 | 13 | 19.7% | |
| custom 5368567102611409831 | 8 | 12.1% | |
| custom 5368811868502646351 | 8 | 12.1% | |
| custom 5400209376516543284 | 8 | 12.1% | |
| custom 5415765357220629550 | 6 | 9.09% | |
| custom 5368651503013747141 | 4 | 6.06% | |
| custom 5413495011738160307 | 4 | 6.06% |
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 12 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 66 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 18 April 2026 to 28 July 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 53688068691607083125custom 54272900214911518613custom 53688118685026463512
Signed ADVOCAT
Свершилось чудо. Мне немного не нравится и я бы хотела переделать, но у меня не сохранился файл и мне удалили криту (случайно) поэтому прогресс не сохранился полностью. Короче как то так🖤 // #арт
custom 53685671026114098313custom 53688068691607083123custom 53688118685026463513
Signed ADVOCAT
Я и Дуникс (ч слева) // #скетч, #арт (?)
custom 53685671026114098313custom 53688068691607083123custom 53688118685026463513
Signed ADVOCAT
Я же не дере, цун-цундере // #скетч
custom 53686515030137471412custom 53688068691607083122custom 53685671026114098311custom 54272900214911518611
Signed ADVOCAT
Новые реакты!!
custom 54272900214911518612
Signed ADVOCAT
Меня учит рендерингу Слюникс // #скетч
custom 53686515030137471412custom 53688068691607083122custom 54272900214911518612custom 53685671026114098311custom 54002093765165432841
Signed ADVOCAT
Work in progress.. // #скетч
custom 54002093765165432842custom 54157653572206295502custom 54272900214911518611
Signed ADVOCAT
Ребят, это единственное что я нарисовала на ноуте за последнее время, извините пожалуйста за такие пропадания, мб скоро будут почаще выходить, надо только оценки подтянуть до 12июльня // #скетч
custom 54002093765165432842custom 54157653572206295502custom 54272900214911518612
Signed ADVOCAT
Ребята, скоро лето, а значит скоро я буду нихуя не делать
Signed ADVOCAT
задумывается об удалении телеграмм канала
Signed ADVOCAT
А тут да с слюникс Тоже заставили // #скетч
custom 54002093765165432841custom 54157653572206295501custom 54272900214911518611
Signed ADVOCAT
Меня луникс заставила выложитьб, на скорую рукк // #скетч
custom 54002093765165432841custom 54157653572206295501custom 54272900214911518611
Signed ADVOCAT
Showing the 12 most recent of 17 posts we hold for @ADVOCAA_t. 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 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“ADVOCAT” (@ADVOCAA_t), 9 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/ADVOCAA_t.
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.