Telegram RegisterThe public register of Telegram
Telegram profile photo for Desipatakas Channel

Channel

Desipatakas Channel

@desipatakasbackups

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

59,248subscribers

-1,666 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002042213319
TypeChannel
Username@desipatakasbackups
DescriptionAll material here is free from copyright issues and shared for informational purposes. This backup complies with Telegram guidelines for DMCA
Created4 March 2024measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/desipatakasbackups

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 68% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

59,24860,91460,0817 August 2026 — 60,914 subscribers7 August 2026 — 60,914 subscribers8 August 2026 — 60,913 subscribers9 August 2026 — 60,872 subscribers10 August 2026 — 60,823 subscribers11 August 2026 — 60,772 subscribers12 August 2026 — 60,732 subscribers13 August 2026 — 60,680 subscribers14 August 2026 — 60,635 subscribers15 August 2026 — 60,501 subscribers16 August 2026 — 60,474 subscribers17 August 2026 — 60,444 subscribers19 August 2026 — 60,376 subscribers20 August 2026 — 60,244 subscribers20 August 2026 — 60,208 subscribers22 August 2026 — 60,120 subscribers24 August 2026 — 59,998 subscribers25 August 2026 — 59,917 subscribers26 August 2026 — 59,848 subscribers27 August 2026 — 59,800 subscribers28 August 2026 — 59,762 subscribers29 August 2026 — 59,696 subscribers30 August 2026 — 59,658 subscribers31 August 2026 — 59,607 subscribers1 September 2026 — 59,565 subscribers2 September 2026 — 59,512 subscribers3 September 2026 — 59,487 subscribers5 September 2026 — 59,434 subscribers8 September 2026 — 59,248 subscribers7 August 20268 September 2026
29 measurements spanning 32 days, net -1,666. 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 58,998–61,164 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
8 Sept 2026, 15:4159,248-186
5 Sept 2026, 07:3859,434-53
3 Sept 2026, 13:1859,487-25
2 Sept 2026, 07:2459,512-53
1 Sept 2026, 08:0559,565-42
31 Aug 2026, 09:5459,607-51
30 Aug 2026, 10:4259,658-38
29 Aug 2026, 08:4459,696-66
28 Aug 2026, 05:1259,762-38
27 Aug 2026, 06:0459,800-48
26 Aug 2026, 03:5259,848-69
25 Aug 2026, 04:0659,917-81
24 Aug 2026, 00:5559,998-122
22 Aug 2026, 09:1260,120-88
20 Aug 2026, 23:4660,208-36
20 Aug 2026, 01:4160,244-132
19 Aug 2026, 00:2260,376-68
17 Aug 2026, 20:5760,444-30
16 Aug 2026, 22:1660,474-27
15 Aug 2026, 15:3360,501first reading

Engagement

3 posts held, back to 4 March 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 69 pages 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 3 posts for this entry, the most recent from 14 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
2

Lifetime counters from Telegram’s own channel header, read 9 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

535 reactions across 2 posts, in 9 distinct kinds. The most used accounts for 66.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
35566.4%
👍6011.2%
🥰305.61%
🤨254.67%
👎244.49%
🔥142.62%
😁132.43%
😈81.50%
👀61.12%

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

Measured over the 3 most recent posts we hold, published 4 March 2024 to 14 August 2025, 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

14 Aug 2025, 17:13 UTC≈92,900 views132 reactionsread 9 September 2026

🔥📢 Welcome to desipatakas🎉 Join our Backup Channel to stay updated. Thank you for your support! 🙏 ⚠️ Please don’t leave this channel. If any of our channels are removed, the new link will be posted here ⬇️⬇️ 🔗 https://t.me/+e2epjihnmGw2MTNh 🔗 https://t.me/+e2epjihnmGw2MTNh 📲 This Is The Private Channel For Amazing Members ❤️ 💥💬 Stay connected and enjoy the content!

113👍8😁7🥰4

13 May 2025, 17:07 UTC≈152,000 views403 reactionsread 9 September 2026

All material here is free from copyright issues and shared for informational purposes. For full access to premium or original content, visit our main channel here: https://t.me/+e2epjihnmGw2MTNh This backup complies with Telegram guidelines and is maintained strictly for safe, non-infringing content sharing. © Content shared on @desipatakasbackups is either original, licensed, or shared with proper rights and permi

242👍52🥰26🤨25👎24🔥14😈8👀6

Showing the 3 most recent of 3 posts we hold for @desipatakasbackups. 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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“Desipatakas Channel” (@desipatakasbackups), 59,248 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/desipatakasbackups.

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.