Telegram RegisterThe public register of Telegram
Telegram profile photo for DECOWSY

Channel

DECOWSY

@decowsy

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

119subscribers

-3 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001718970572
TypeChannel
Username@decowsy
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live11 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/decowsy

Growth

1191231219 August 2026 — 122 subscribers10 August 2026 — 122 subscribers10 August 2026 — 123 subscribers17 August 2026 — 122 subscribers25 August 2026 — 121 subscribers2 September 2026 — 122 subscribers11 September 2026 — 119 subscribers9 August 202611 September 2026
7 measurements spanning 32 days, net -3. 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 118–124 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 08:17119-3
2 Sept 2026, 01:24122+1
25 Aug 2026, 04:16121-1
17 Aug 2026, 14:08122-1
10 Aug 2026, 10:01123+1
10 Aug 2026, 00:00122no change
9 Aug 2026, 23:47122first reading

Engagement

13 posts held, back to 8 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 page of 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 13 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
18s
Average length
9s

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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8740.8%
🔥6028.2%
❤‍🔥3014.1%
🍾188.45%
💘146.57%
💅20.939%
💊10.469%
🥰10.469%

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

Measured over the 13 most recent posts we hold, published 8 July 2026 to 5 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

5 Aug 2026, 17:35 UTC46 views19 reactionsread 10 August 2026
Photo

*фанарт для алишези

10❤‍🔥5🔥2🍾1💘1

Signed зелëная негодяйка, чаеед и моховед

3 Aug 2026, 21:47 UTC62 views9 reactionsread 10 August 2026
Video

*йа не планировала ето доделвыать но онокакто само получилось чему я оченб рада

🔥5❤‍🔥3🍾1

Signed зелëная негодяйка, чаеед и моховед

2 Aug 2026, 22:07 UTC65 views18 reactionsread 10 August 2026
Video

*от нечево делать наресавала вэээээээ :Р :Ь

💘11🔥3🍾21❤‍🔥1

Signed зелëная негодяйка, чаеед и моховед

2 Aug 2026, 18:56 UTC63 views19 reactionsread 10 August 2026
Photo

*СМАТРИТЕ КАКУБ КРАСАТУ МНЕ ВАЛЬФРАМУШКА НАРЕСАВАЛ ЙА В ВОСТОРГН

🔥114❤‍🔥1🍾1💅1💘1

Signed зелëная негодяйка, чаеед и моховед

2 Aug 2026, 13:37 UTC61 views19 reactionsread 10 August 2026
Photo

*старые скетчи, забыла когдато выложитб *ресавала правой рукой [йа левша]

❤‍🔥105🔥2🍾1💊1

Signed зелëная негодяйка, чаеед и моховед

28 Jul 2026, 20:44 UTC215 views25 reactionsread 10 August 2026
Photo

*первоя партия ючей, йухуу!! отдохну денëк-другой и прадолжу ресавать :D [напоминаю што остались ищо слоты]

14❤‍🔥6🍾3💅1🔥1

Signed зелëная негодяйка, чаеед и моховед

27 Jul 2026, 20:14 UTC100 views23 reactionsread 10 August 2026
Photo

*случяйно сделоть персанажа ево полной противоположностю ещо нужно уметь *редизайн каторым йа довольна до жути :DD

13🔥7❤‍🔥1🍾1💘1

Signed зелëная негодяйка, чаеед и моховед

16 Jul 2026, 14:01 UTC161 views10 reactionsread 10 August 2026
Photo

*юч или типо тово :Р :Ь занято слотов: 9/10 • цена 200р • дедлайн 4 дня с момента оплаты • оплата на т-банк по номеру карты перед началом работы. в случае просрочки дедлайна по моей вине верну половину суммы • можно менять выражение мордочки, положение ушек и хвоста, цвет фона • правки принимаются до начала рендера • чтобы заказать пишите в комментарии под постом. я сама напишу в лс когда подойдёт ваша очередь исп

7🔥2🍾1

Signed зелëная негодяйка, чаеед и моховед

14 Jul 2026, 21:38 UTC138 views17 reactionsread 10 August 2026
Photo

*йа доделала редмзайн ещо один

9🔥6🍾2

Signed зелëная негодяйка, чаеед и моховед

13 Jul 2026, 10:19 UTC131 views19 reactionsread 10 August 2026
Photo

*аээаэ ну это карлче типо редизайн ^0^

🔥123🍾3🥰1

Signed зелëная негодяйка, чаеед и моховед

8 Jul 2026, 13:30 UTC183 views19 reactionsread 10 August 2026
Photo

*а жто давнишний скетч с моими любимками одночлен и дурнем

13🔥5🍾1

Signed зелëная негодяйка, чаеед и моховед

Showing the 12 most recent of 13 posts we hold for @decowsy. 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.

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.

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

“DECOWSY” (@decowsy), 119 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/decowsy.

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.