Telegram RegisterThe public register of Telegram
Telegram profile photo for LITEAPKS.COM - Official 🔥

Channel

LITEAPKS.COM - Official 🔥

@liteapks

Not marked by Telegram, checked 26 August 2026

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

2,009,860subscribers

-13,961 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1001727760118
TypeChannel
Username@liteapks
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/liteapks

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 72% 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

2,009,8602,023,8212,016,840.56 August 2026 — 2,023,821 subscribers7 August 2026 — 2,023,524 subscribers7 August 2026 — 2,023,524 subscribers8 August 2026 — 2,023,229 subscribers9 August 2026 — 2,023,211 subscribers10 August 2026 — 2,022,769 subscribers11 August 2026 — 2,022,459 subscribers12 August 2026 — 2,021,947 subscribers13 August 2026 — 2,021,649 subscribers14 August 2026 — 2,020,952 subscribers16 August 2026 — 2,020,538 subscribers17 August 2026 — 2,019,786 subscribers18 August 2026 — 2,022,149 subscribers19 August 2026 — 2,023,070 subscribers20 August 2026 — 2,023,258 subscribers22 August 2026 — 2,022,852 subscribers23 August 2026 — 2,021,981 subscribers25 August 2026 — 2,021,116 subscribers26 August 2026 — 2,020,419 subscribers27 August 2026 — 2,019,832 subscribers28 August 2026 — 2,019,493 subscribers28 August 2026 — 2,018,470 subscribers30 August 2026 — 2,017,373 subscribers31 August 2026 — 2,016,096 subscribers1 September 2026 — 2,014,644 subscribers2 September 2026 — 2,016,208 subscribers3 September 2026 — 2,015,101 subscribers5 September 2026 — 2,013,773 subscribers8 September 2026 — 2,009,860 subscribers6 August 20268 September 2026
29 measurements spanning 32 days, net -13,961. 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 2,007,766–2,025,915 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, 05:382,009,860-3,913
5 Sept 2026, 01:582,013,773-1,328
3 Sept 2026, 09:032,015,101-1,107
2 Sept 2026, 00:542,016,208+1,564
1 Sept 2026, 03:372,014,644-1,452
31 Aug 2026, 03:562,016,096-1,277
30 Aug 2026, 01:172,017,373-1,097
28 Aug 2026, 22:262,018,470-1,023
28 Aug 2026, 00:162,019,493-339
27 Aug 2026, 02:452,019,832-587
26 Aug 2026, 05:262,020,419-697
25 Aug 2026, 03:522,021,116-865
23 Aug 2026, 21:442,021,981-871
22 Aug 2026, 02:182,022,852-406
20 Aug 2026, 16:342,023,258+188
19 Aug 2026, 19:432,023,070+921
18 Aug 2026, 16:162,022,149+2,363
17 Aug 2026, 17:472,019,786-752
16 Aug 2026, 16:062,020,538-414
14 Aug 2026, 23:462,020,952first reading

Engagement

No public post preview. We read this entry on 7 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

Mentions

Named by 6 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“LITEAPKS.COM - Official 🔥” (@liteapks), 2,009,860 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/liteapks.

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.