Telegram RegisterThe public register of Telegram
Telegram profile photo for Appsmodz

Channel

Appsmodz

@AppsModz

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

5,792subscribers

-341 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001324509919
TypeChannel
Username@AppsModz
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live29 October 2026
Measurements held24
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/AppsModz

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 81% 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

5,7926,1335,962.57 August 2026 — 6,133 subscribers7 August 2026 — 6,131 subscribers10 August 2026 — 6,122 subscribers13 August 2026 — 6,105 subscribers16 August 2026 — 6,093 subscribers19 August 2026 — 6,084 subscribers22 August 2026 — 6,078 subscribers25 August 2026 — 6,066 subscribers28 August 2026 — 6,056 subscribers29 August 2026 — 6,056 subscribers31 August 2026 — 6,044 subscribers3 September 2026 — 6,036 subscribers9 September 2026 — 6,013 subscribers13 September 2026 — 5,998 subscribers17 September 2026 — 5,990 subscribers26 September 2026 — 5,924 subscribers5 October 2026 — 5,876 subscribers11 October 2026 — 5,856 subscribers14 October 2026 — 5,843 subscribers17 October 2026 — 5,839 subscribers20 October 2026 — 5,826 subscribers23 October 2026 — 5,814 subscribers26 October 2026 — 5,800 subscribers29 October 2026 — 5,792 subscribers7 August 202629 October 2026
24 measurements spanning 83 days, net -341. 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 5,741–6,184 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
29 Oct 2026, 04:015,792-8
26 Oct 2026, 12:175,800-14
23 Oct 2026, 14:095,814-12
20 Oct 2026, 22:395,826-13
17 Oct 2026, 13:285,839-4
14 Oct 2026, 13:315,843-13
11 Oct 2026, 06:185,856-20
5 Oct 2026, 00:555,876-48
26 Sept 2026, 07:185,924-66
17 Sept 2026, 11:195,990-8
13 Sept 2026, 05:025,998-15
9 Sept 2026, 09:386,013-23
3 Sept 2026, 16:216,036-8
31 Aug 2026, 18:036,044-12
29 Aug 2026, 18:346,056no change
28 Aug 2026, 18:446,056-10
25 Aug 2026, 09:326,066-12
22 Aug 2026, 12:046,078-6
19 Aug 2026, 13:066,084-9
16 Aug 2026, 20:336,093first 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“Appsmodz” (@AppsModz), 5,792 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/AppsModz.

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.