Telegram RegisterThe public register of Telegram
Telegram profile photo for CYBERWORKS [art, fursuit,comms..]

Channel

CYBERWORKS [art, fursuit,comms..]

@PDCyberArt

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

139subscribers

+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-1001581592283
TypeChannel
Username@PDCyberArt
Created11 July 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live23 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/PDCyberArt

Growth

138139138.57 August 2026 — 138 subscribers8 August 2026 — 138 subscribers23 August 2026 — 139 subscribers7 August 202623 August 2026
3 measurements spanning 16 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 138–139 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 19:44139+1
8 Aug 2026, 23:01138no change
7 Aug 2026, 19:57138first reading

Engagement

6 posts held, back to 28 January 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 6 posts for this entry, the most recent from 12 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
21s
Average length
11s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

75 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 92.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6992.0%
🔥45.33%
👀11.33%
😱11.33%

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

Measured over the 6 most recent posts we hold, published 28 January 2026 to 12 May 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

12 May 2026, 16:58 UTC166 views13 reactionsread 8 August 2026
Photo

Love is in the air! ❤️ Art commission from Siber to Wolvinny & Jake for their lovely wedding! 😍

13

8 Apr 2026, 10:02 UTC246 views11 reactionsread 8 August 2026
Photo

This boyo is excited to see ya! 🐶🐾 Art commission for Haki’s Birthday yesterday! 🎉🎉🎂

11

28 Feb 2026, 11:03 UTC283 views11 reactionsread 8 August 2026
Photo

Finished up this tail for a stripey Tiger! 🐯 You might have seen him proudly swaying around on NFC

11

26 Feb 2026, 15:24 UTC248 views16 reactionsread 8 August 2026
Photo

Tiger pattern in the works! The most complex pattern I’ve done so far 🫣🐯 — I’m still down with concrud from NFC 🤧 so work will be minimal this week… I’ll be back up and running in the studio next week! 💪

10🔥4👀1😱1

22 Feb 2026, 10:58 UTC241 views9 reactionsread 8 August 2026
Photo

Anyone I haven’t seen yet? 🤗💙💙

9

28 Jan 2026, 21:30 UTC296 views15 reactionsread 8 August 2026
Photo

📸 Some cool photos of me as PD and Cyber, shot by @Hojo_be at FLÜÜFFF! I wanted to show them here 🤍

15

Showing the 6 most recent of 6 posts we hold for @PDCyberArt. 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.

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

“CYBERWORKS [art, fursuit,comms..]” (@PDCyberArt), 139 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/PDCyberArt.

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.