Telegram RegisterThe public register of Telegram
Telegram profile photo for DrPie's Sketch Channel

Channel

DrPie's Sketch Channel

@drpieart

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

100subscribers

+0 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-1002553458063
TypeChannel
Username@drpieart
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live24 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/drpieart

Growth

9910099.58 August 2026 — 100 subscribers9 August 2026 — 100 subscribers16 August 2026 — 99 subscribers24 August 2026 — 100 subscribers8 August 202624 August 2026
4 measurements spanning 16 days. 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 99–100 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 15:52100+1
16 Aug 2026, 17:4799-1
9 Aug 2026, 10:47100no change
8 Aug 2026, 04:15100first reading

Engagement

17 posts held, back to 12 June 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
44.5%
avg views ÷ 100 subscribers
Avg views / post
44.5
2 posts measured
Reaction rate
20.2%
reactions ÷ views · ER floor
Posts in window
2
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 8 August 2026
Posts held17 (12 June 20268 August 2026)
Views total89
Reactions total18
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 10:47 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

154 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 96.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
14896.1%
🤣31.95%
👏10.649%
💯10.649%
🔥10.649%

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 17 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 154reactions 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 12 June 2026 to 8 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

8 Aug 2026, 16:25 UTC45 views7 reactionsread 9 August 2026
Photo

I ordered a Cynder hoodie online. Guess we all know what that means. Now I just gotta learn to draw her...

7

6 Aug 2026, 23:52 UTC44 views11 reactionsread 9 August 2026
Forwarded from @joltinkart

https://bsky.app/profile/joltink.com/post/3msgj6d3tqk22

11

25 Jul 2026, 22:50 UTC137 views11 reactionsread 9 August 2026
Photo

I'm sure at one point it seemed so intuitive to have run and attack on the same button

11

23 Jul 2026, 06:01 UTC143 views8 reactionsread 9 August 2026
Photo

Had an urge to quickly doodle a cute monkey before bed

8

16 Jul 2026, 18:21 UTC153 views9 reactionsread 9 August 2026
Photo

I popped into a Discord stream to discover Boofan22 started up Platinum and chose to play as Peak. So naturally now I have to doodle this =P I couldn't decide on an amount of Identifier and whether to go Anime Hair or Game Hair (Boo's also streaming the anime for us) so have all 8 variants.

8💯1

13 Jul 2026, 04:15 UTC168 views5 reactionsread 9 August 2026
Photo

I had a little bit of free time at work today to doodle munkee (I played DKC2 with Zilch earlier today and kept falling down most of a vertical climbing level)

5

12 Jul 2026, 05:40 UTC849 views9 reactionsread 9 August 2026
Photo

So I got put in the mood to doodle more Diddy Kong, and then Zilch forgot the rule of never make requests/suggestions to me without specifying that it's not meant to be you. Come on, Joltink JUST fell for it a couple days ago.

9

10 Jul 2026, 18:32 UTC117 views11 reactionsread 9 August 2026
Photo

Joltink also suggested I draw Bombchu TF, and who's a better muse for that than TrevorFox?

10🔥1

10 Jul 2026, 18:09 UTC635 views11 reactionsread 9 August 2026
Photo

Joltink suggested I draw a TF into one of those small Jurassic World dino plushies. He forgot to specify who becomes the plush.

11

7 Jul 2026, 17:03 UTC142 views12 reactionsread 9 August 2026
Photo

Yeah yeah, the new Universal park is lacking in shade most parts of the day. Stay out of the spots for character meet-&-greets though.

12

24 Jun 2026, 16:02 UTC219 views8 reactionsread 9 August 2026
Photo

Happy Make A Terrible Comic Day! Also coincidentally Happy 6/24 Day!

8

Showing the 12 most recent of 17 posts we hold for @drpieart. 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 — 863,265 of 1,621,120entries 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.

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.

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

“DrPie's Sketch Channel” (@drpieart), 100 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/drpieart.

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.