Telegram RegisterThe public register of Telegram

Channel

ADVOCAT

@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.

Register entry

Telegram ID-1003582887628
TypeChannel
Username@ADVOCAA_t
CreatedBetween 1 December 2025 and 18 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live15 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/ADVOCAA_t

Growth

914 Aug 2026, 12:16 — 9 subscribers15 Aug 2026, 02:57 — 9 subscribers14 Aug 2026, 12:1615 Aug 2026, 02:57
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 02:579no change
14 Aug 2026, 12:169first reading

Engagement

17 posts held, back to 18 April 2026the 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
122.2%
avg views ÷ 9 subscribers
Avg views / post
11.0
1 post measured
Reaction rate
90.9%
reactions ÷ views · ER floor
Posts in window
1
of 17 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 July 2026
Posts held17 (18 April 202628 July 2026)
Views total11
Reactions total10
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 12:16 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.

Reaction mix

66 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 22.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53688068691607083121522.7%
custom 54272900214911518611319.7%
custom 5368567102611409831812.1%
custom 5368811868502646351812.1%
custom 5400209376516543284812.1%
custom 541576535722062955069.09%
custom 536865150301374714146.06%
custom 541349501173816030746.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 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 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 66reactions 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.

Recent posts

28 Jul 2026, 22:45 UTC11 views10 reactionsread 14 August 2026
Photo

Привет привет, давно не виделись (то что «недорисовано» так и должно быть, лол) // #скетч

custom 53688068691607083125custom 54272900214911518613custom 53688118685026463512

Signed ADVOCAT

1 Jul 2026, 21:26 UTC54 views9 reactionsread 14 August 2026
Photo

Свершилось чудо. Мне немного не нравится и я бы хотела переделать, но у меня не сохранился файл и мне удалили криту (случайно) поэтому прогресс не сохранился полностью. Короче как то так🖤 // #арт

custom 53685671026114098313custom 53688068691607083123custom 53688118685026463513

Signed ADVOCAT

30 Jun 2026, 19:33 UTC81 views9 reactionsread 14 August 2026
Photo

Я и Дуникс (ч слева) // #скетч, #арт (?)

custom 53685671026114098313custom 53688068691607083123custom 53688118685026463513

Signed ADVOCAT

28 Jun 2026, 20:02 UTC43 views6 reactionsread 14 August 2026
Photo

Я же не дере, цун-цундере // #скетч

custom 53686515030137471412custom 53688068691607083122custom 53685671026114098311custom 54272900214911518611

Signed ADVOCAT

28 Jun 2026, 12:55 UTC36 views2 reactionsread 14 August 2026

Новые реакты!!

custom 54272900214911518612

Signed ADVOCAT

28 Jun 2026, 12:39 UTC35 views8 reactionsread 14 August 2026
Photo

Меня учит рендерингу Слюникс // #скетч

custom 53686515030137471412custom 53688068691607083122custom 54272900214911518612custom 53685671026114098311custom 54002093765165432841

Signed ADVOCAT

15 Jun 2026, 19:15 UTC51 views5 reactionsread 14 August 2026
Photo

Work in progress.. // #скетч

custom 54002093765165432842custom 54157653572206295502custom 54272900214911518611

Signed ADVOCAT

3 Jun 2026, 19:01 UTC53 views6 reactionsread 14 August 2026
Photo

Ребят, это единственное что я нарисовала на ноуте за последнее время, извините пожалуйста за такие пропадания, мб скоро будут почаще выходить, надо только оценки подтянуть до 12июльня // #скетч

custom 54002093765165432842custom 54157653572206295502custom 54272900214911518612

Signed ADVOCAT

12 May 2026, 14:23 UTC49 viewsread 14 August 2026

Ребята, скоро лето, а значит скоро я буду нихуя не делать

Signed ADVOCAT

12 May 2026, 14:23 UTC51 viewsread 14 August 2026
Forwarded from @cheremshaotrvaa

задумывается об удалении телеграмм канала

Signed ADVOCAT

3 May 2026, 08:26 UTC61 views3 reactionsread 14 August 2026
Photo

А тут да с слюникс Тоже заставили // #скетч

custom 54002093765165432841custom 54157653572206295501custom 54272900214911518611

Signed ADVOCAT

3 May 2026, 08:24 UTC52 views3 reactionsread 14 August 2026
Photo

Меня луникс заставила выложитьб, на скорую рукк // #скетч

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.

Citation-graph rank

Citation-graph rank — 276,162 of 1,480,688entries 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

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.

Mentions

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.

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.

“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.