Telegram RegisterThe public register of Telegram
Telegram profile photo for photoshopediussoftware

Channel

photoshopediussoftware

@photoshopediussoftware

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

30subscribers

-6,085 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-1001665462657
TypeChannel
Username@photoshopediussoftware
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live12 November 2026
Measurements held16
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/photoshopediussoftware

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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

276,1713,0997 August 2026 — 6,115 subscribers8 August 2026 — 6,117 subscribers11 August 2026 — 6,111 subscribers14 August 2026 — 6,110 subscribers17 August 2026 — 6,109 subscribers20 August 2026 — 6,121 subscribers24 August 2026 — 6,128 subscribers27 August 2026 — 6,127 subscribers29 August 2026 — 6,127 subscribers30 August 2026 — 6,133 subscribers2 September 2026 — 6,130 subscribers7 September 2026 — 6,147 subscribers11 September 2026 — 6,164 subscribers16 September 2026 — 6,171 subscribers4 November 2026 — 27 subscribers12 November 2026 — 30 subscribers307 August 202612 November 2026
16 measurements spanning 97 days, net -6,085. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 08:0830+3
4 Nov 2026, 19:5627-6,144
16 Sept 2026, 03:586,171+7
11 Sept 2026, 23:576,164+17
7 Sept 2026, 23:386,147+17
2 Sept 2026, 21:456,130-3
30 Aug 2026, 09:546,133+6
29 Aug 2026, 11:526,127no change
27 Aug 2026, 02:156,127-1
24 Aug 2026, 11:386,128+7
20 Aug 2026, 10:076,121+12
17 Aug 2026, 17:146,109-1
14 Aug 2026, 21:086,110-1
11 Aug 2026, 09:446,111-6
8 Aug 2026, 08:006,117+2
7 Aug 2026, 14:386,115first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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

“photoshopediussoftware” (@photoshopediussoftware), 30 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/photoshopediussoftware.

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.