Telegram RegisterThe public register of Telegram
Telegram profile photo for зверюга

Channel

зверюга

@zverrrruga

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

86subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002281883443
TypeChannel
Username@zverrrruga
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/zverrrruga

Growth

858685.57 August 2026 — 85 subscribers9 August 2026 — 85 subscribers14 August 2026 — 86 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net +1. 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 85–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:3586+1
9 Aug 2026, 17:0085no change
7 Aug 2026, 14:3985first reading

Engagement

16 posts held, back to 22 March 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 21 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

205 reactions across 16 posts, in 15 distinct kinds. The most used accounts for 25.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5325.9%
custom 53866465913502515193919.0%
custom 52877697397523958132311.2%
custom 53076128623220573052110.2%
custom 5289524710634180115146.83%
🎉104.88%
😈94.39%
🔥83.90%
👾73.41%
custom 533488422961441610662.93%
🍓62.93%
custom 533686499981185420641.95%
🏆20.976%
💘20.976%
🐳10.488%

Custom emoji. 6 of the rows above are 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 16 of the 16 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 205reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 22 March 2026 to 21 June 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

21 Jun 2026, 19:51 UTC45 views10 reactionsread 9 August 2026
Photo

нашла силы дальше выдумывать историю про двух водяных братьев 🌀🪷 (вдохновленных....листовкой с бутылками воды прости господи) я в тильте, если честно, очень давно не рисовала и это дает о себе знать

4custom 53076128623220573053💘2🏆1

10 Jun 2026, 09:52 UTC69 views17 reactionsread 9 August 2026
Photo

урааа открытка Сашке на дэрэ всем смотреть 🎶🎶🎶

🎉96custom 52877697397523958132

19 May 2026, 20:12 UTC92 views13 reactionsread 9 August 2026
Photo

раскраски по номерам скачать платно 🤩🖱

👾6custom 53866465913502515194custom 53076128623220573053

18 May 2026, 05:20 UTC89 views15 reactionsread 9 August 2026
Photo

вчера еще лайн сделала посмотрите, какой крутой в туфлях, с пакетом 🤩

8custom 52877697397523958134custom 53076128623220573052👾1

17 May 2026, 17:23 UTC71 views11 reactionsread 9 August 2026
Photo

природа настолько очистилась, что зверюга порисовала (пока конечно только скетчевый вариант полноценной работы) это компьютерный челик, вдохновленный, не поверите, одной из дирекций на моей любимой работе дирекция внедрения информационных систем 🤩 я оч давно делилась скетчем, но он мне сейчас не нра поэтому я бахнула такую версию (над летающей позой просидела час, старею) ☁️🌟

custom 530761286232205730572🎉1🏆1

11 May 2026, 13:02 UTC71 views11 reactionsread 9 August 2026
Forwarded from @lumayapwhoPhoto

Реквест для @zverrrrek Аж фон выбросила с атсилками😘😘😘😘 💪 Лол, щас наконец-то буду рисовать уро #СкетчРекв

custom 53866465913502515196😈2custom 528776973975239581321

11 May 2026, 13:02 UTC71 views5 reactionsread 9 August 2026

УРА МОЮ ЯЩЕРИЦУ НАРИСОВАЛИ!!!

custom 538664659135025151941

3 May 2026, 08:02 UTC95 views11 reactionsread 9 August 2026

ОФИГЕТЬ ЗАЦЕН ВЫШЕ ЧЕ У МЕНЯ МЕЛКАЯ НАРИСОВАЛА!!! (это мой персонаж кста)

6custom 52895247106341801153custom 52877697397523958132

3 May 2026, 08:01 UTC88 views12 reactionsread 9 August 2026
Photo

король пердолик, точнее сердолик ;)

🔥6custom 53866465913502515193custom 528776973975239581321

19 Apr 2026, 11:01 UTC88 views16 reactionsread 9 August 2026
Photo

ура, артик лучшей подруге Виолеттке на др!!!! поздравляю, всего хо ро ше го!!!!!😘😘😘

9custom 52877697397523958134🔥2custom 52895247106341801151

12 Apr 2026, 09:18 UTC95 views20 reactionsread 9 August 2026
Photo

как же прекрасен яичный спас

custom 538664659135025151910custom 53348842296144161066custom 52877697397523958134

8 Apr 2026, 12:39 UTC95 views9 reactionsread 9 August 2026

походу все серьезно подумали, что теперь я буду нифига не рисовать, но уже в Максе нет! приходите в мою старую группу вк, если тг уже не робит (не смогли смириться с поражением... и куда вас это привело? снова ко мне...) https://vk.ru/freneza.besto

custom 53076128623220573054custom 52877697397523958132custom 53866465913502515192🐳1

Showing the 12 most recent of 16 posts we hold for @zverrrruga. 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 — 1,331,088 of 1,481,217entries 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

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.

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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“зверюга” (@zverrrruga), 86 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/zverrrruga.

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.