Telegram RegisterThe public register of Telegram
Telegram profile photo for Adobe Creative Cloud - Reseller @acc_resellerbot

Channel

Adobe Creative Cloud - Reseller @acc_resellerbot

@acc_reseller

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

71subscribers

+22 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-1003830633253
TypeChannel
Username@acc_reseller
Created11 April 2026 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live4 November 2026
Measurements held10
Confirmed unchanged2 times, most recently 4 November 2026
On Telegramt.me/acc_reseller

Topic

Software piracy — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 the other topics.

Growth

4971607 August 2026 — 49 subscribers10 August 2026 — 49 subscribers15 August 2026 — 51 subscribers22 August 2026 — 53 subscribers4 September 2026 — 52 subscribers25 September 2026 — 56 subscribers7 October 2026 — 59 subscribers14 October 2026 — 63 subscribers22 October 2026 — 70 subscribers29 October 2026 — 71 subscribers7 August 202629 October 2026
10 measurements spanning 82 days, net +22. 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 46–74 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Oct 2026, 04:2871+1
22 Oct 2026, 20:3170+7
14 Oct 2026, 19:1663+4
7 Oct 2026, 02:2159+3
25 Sept 2026, 12:2056+4
4 Sept 2026, 14:3852-1
22 Aug 2026, 00:4553+2
15 Aug 2026, 16:0451+2
10 Aug 2026, 12:1649no change
7 Aug 2026, 19:3349first reading

Engagement

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

Reaction mix

10 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩550.0%
🤮330.0%
❤220.0%

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

Measured over the 14 most recent posts we hold, published 11 April 2026 to 6 July 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 Jul 2026, 22:27 UTC200 views3 reactionsread 10 August 2026

Adobe Individual Accounts Available We are now taking limited orders for Adobe Individual accounts. These are stable individual accounts, not team/enterprise accounts, so you don’t have to worry about sudden team shutdowns or access issues. Stock is limited and orders will be accepted on a first-come, first-served basis. Buy before the current stock ends. Once slots are full, new orders will only open when fresh …

❤2🤮1

22 Jun 2026, 05:30 UTC283 views2 reactionsread 10 August 2026

Updated version: 📢 New Update Our bot is now in testing phase, but you can already use it. ✅ Individual Plans have been added ✅ Full stable plans ✅ Warranty included ✅ Best for long-term use Also available: 🔑 Redeemable Keys • Non-warranty • Key-based activation 🤖 AI Credits Top-Up 🖼 Adobe Stock 🎨 Behance Pro Check prices and availability here: 👉 @acc_resellerbot

🤮2

22 Jun 2026, 04:00 UTC224 views1 reactionsread 10 August 2026

📢 New Update We now have Adobe Individual Plans available. ✅ Full stable plans ✅ Warranty included ✅ Best for long-term use ✅ Individual account setup Also available: 🔑 Redeemable Keys • Non-warranty • For users who prefer key-based activation 💰 For latest prices and availability, DM @adobe_cart

💩1

17 Jun 2026, 12:59 UTC213 views1 reactionsread 10 August 2026

Send our query system to your customers. If their own organization becomes invalid, they can replace it with a new one by themselves.

💩1

17 Jun 2026, 08:28 UTC176 views1 reactionsread 10 August 2026

The server is currently experiencing severe lag, and we are working urgently to fix it.

💩1

17 Jun 2026, 06:41 UTC173 views1 reactionsread 10 August 2026

we are in the process of repair, please be patient, we will notify you here.

💩1

26 May 2026, 03:33 UTC160 views1 reactionsread 10 August 2026
Photo

We have also updated the status display within our query system, allowing our clients to clearly identify the actual status of the organizations they search for. If an organization is operating normally, the status displays as: Team status: Normal If an organization is inactive, the status displays as: Team status: Inactive If an organization is currently undergoing maintenance or repair, the status displays as: Team…

💩1

25 May 2026, 19:46 UTCviews —

Channel name was changed to «Adobe Creative Cloud - Reseller @acc_resellerbot»

11 Apr 2026, 11:22 UTC178 viewsread 10 August 2026

A gentleman loves money, takes it wisely, and will never be a liar. Integrity management, small profits and quick sales, make friends, common prosperity.

Showing the 12 most recent of 14 posts we hold for @acc_reseller. 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“Adobe Creative Cloud - Reseller @acc_resellerbot” (@acc_reseller), 71 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/acc_reseller.

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.