Telegram RegisterThe public register of Telegram

Channel

{рест} Шаня рисует

@shanes_drivell

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

91subscribers

+5 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003576781315
TypeChannel
Username@shanes_drivell
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/shanes_drivell

Growth

869188.58 August 2026 — 86 subscribers9 August 2026 — 86 subscribers15 August 2026 — 91 subscribers8 August 202615 August 2026
3 measurements spanning 7 days, net +5. 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–92 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 02:0791+5
9 Aug 2026, 16:1886no change
8 Aug 2026, 13:3086first reading

Engagement

12 posts held, back to 15 July 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
79.9%
avg views ÷ 91 subscribers
Avg views / post
72.7
7 posts measured
Reaction rate
11.2%
reactions ÷ views · ER floor
Posts in window
8
of 12 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 6 August 2026
Posts held12 (15 July 20266 August 2026)
Views total509
Reactions total57
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 16:18 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

92 reactions across 10 posts, in 12 distinct kinds. The most used accounts for 31.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 59697550381998474482931.5%
custom 53145213301026024801516.3%
1314.1%
custom 53751932063569955561213.0%
custom 546522523423372378377.61%
🥰44.35%
🍓33.26%
👀33.26%
custom 524706687585410308522.17%
custom 537558874707515297522.17%
custom 537512331005921940911.09%
🔥11.09%

Custom emoji. 7 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 10 of the 12 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 92reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 15 July 2026 to 6 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.

Recent posts

6 Aug 2026, 12:26 UTC47 views20 reactionsread 9 August 2026
Photo

я вернувся:3

custom 53751932063569955569custom 59697550381998474485🍓3custom 53755887470751529752custom 53751233100592194091

31 Jul 2026, 21:29 UTC81 views4 reactionsread 9 August 2026
Forwarded from @Az0t3kPhoto

Набор на интерактив — 🔤🔤🔤🔤🔤🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤🔤 — В чем суть? Организатор кидает первому в очереди участнику заблюренную версию картинки, а тот, в свою очередь, рисуе то, что увидел. После окончания работы художник передаёт замыленную версию работы следующему в очереди, и так пока не дойдёт до последнего человека. — Как принять участие? Что-бы попасть в планшет, от вас требуется: • Репост этого поста к себе в канал. (р

custom 59697550381998474484

31 Jul 2026, 21:24 UTC66 views3 reactionsread 9 August 2026
Photo

┊ . 𑄽୧ ♡💜💜💜💜💜💜💜 ° 💜💜💜💜💜💜💜 ╰︎╮ ◖🤩: .` Участники ° ╰︎────🤍🤍🤍🤍 🤩- - shmakokrak - [ тык ] 🤩- - Ari - [ тык ] 🤩- - Керосин - [ тык ] 🤩- - zendomatrix - [ тык ] 🤩- - покофон - [ тык ] 🤩- - Огние - [ тык ] 🤩- - shanerr11 - [ тык ] 🤩- - Арти - [ тык ] 🤩- - Bat - [ тык ] 🤩- - Кирпич - [ тык ] 🤩- - меверти - [ тык ] 🤩- - Ratt- - [ тык ] 🤩- - Randy - [ тык ] 🤩- - Варвар - [ тык ] 🤩- - Софа - [

custom 59697550381998474483

31 Jul 2026, 17:13 UTC67 views2 reactionsread 9 August 2026

емае спасибо🙏

custom 59697550381998474482

31 Jul 2026, 17:13 UTC63 views13 reactionsread 9 August 2026
Forwarded from @Kv4zaaaRPhoto

гифт для @shanes_drivell не буду против репостов ес че❤️

custom 54652252342337237837custom 52470668758541030852custom 53751932063569955562custom 59697550381998474482

16 Jul 2026, 17:35 UTC128 views13 reactionsread 9 August 2026

уезжаю на три недели, хз будет ли инет

7👀3custom 59697550381998474483

15 Jul 2026, 11:20 UTC140 views22 reactionsread 9 August 2026
Photo

в комменты кину потом эти же сканы но без фильтров, мне они пипец нравятся

custom 5314521330102602480114🥰4🔥1custom 53751932063569955561custom 59697550381998474481

15 Jul 2026, 11:10 UTC111 views5 reactionsread 9 August 2026

ребят жеск прошу прощения что столько репостов, они все будут держаться сутки если нет условия что это лота/розыгрыш и подобное а пока ждите картиночное маслом, я пытался

custom 59697550381998474485

15 Jul 2026, 11:08 UTC107 viewsread 9 August 2026
Forwarded from @mmenkent4Photo

ЛОТА НА КАРТИНКИ (вообще должна была быть на 100 но я немножко про нее забыла) ПРИЗЫ: всего будет три места и каждое получает кастом или арт любого формата(до 2 персонажей на картинке) УСЛОВИЯ: 1. подписка на канал 2. репост поста 3 друзьям/в свой тгк/активный чат 3. отписаться в комментарии под постом(номер не нужен, я сама всем раздам перед результатами) 4. твинки/незаинтересованных в призе друзей задействовать д

15 Jul 2026, 04:50 UTC83 views8 reactionsread 9 August 2026
Forwarded from @policattalePhoto

#PortfolioDay Может быть я ещё немного успею, хех работа убивает...

custom 531452133010260248042custom 59697550381998474482

Showing the 12 most recent of 12 posts we hold for @shanes_drivell. 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 — 562,069 of 1,350,102entries 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 4 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.

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.

“{рест} Шаня рисует” (@shanes_drivell), 91 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/shanes_drivell.

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.