Telegram RegisterThe public register of Telegram
Telegram profile photo for Loot Zone™

Channel

Loot Zone™

@lootzoner

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

1,920subscribers

-389 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001615413411
TypeChannel
Username@lootzoner
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 September 2026
Last confirmed live3 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/lootzoner

Topic

Giveaways & airdrops — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

1,9202,3092,114.57 August 2026 — 2,309 subscribers11 August 2026 — 2,283 subscribers14 August 2026 — 2,269 subscribers17 August 2026 — 2,249 subscribers20 August 2026 — 2,240 subscribers24 August 2026 — 2,227 subscribers27 August 2026 — 2,215 subscribers30 August 2026 — 2,199 subscribers2 September 2026 — 2,181 subscribers7 September 2026 — 2,153 subscribers11 September 2026 — 2,138 subscribers15 September 2026 — 2,127 subscribers19 September 2026 — 2,127 subscribers26 September 2026 — 2,075 subscribers5 October 2026 — 2,039 subscribers11 October 2026 — 2,006 subscribers15 October 2026 — 1,994 subscribers18 October 2026 — 1,981 subscribers21 October 2026 — 1,970 subscribers24 October 2026 — 1,958 subscribers28 October 2026 — 1,951 subscribers31 October 2026 — 1,937 subscribers3 November 2026 — 1,920 subscribers7 August 20263 November 2026
23 measurements spanning 88 days, net -389. 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 1,862–2,367 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
3 Nov 2026, 08:081,920-17
31 Oct 2026, 03:101,937-14
28 Oct 2026, 04:371,951-7
24 Oct 2026, 20:091,958-12
21 Oct 2026, 13:511,970-11
18 Oct 2026, 14:571,981-13
15 Oct 2026, 06:581,994-12
11 Oct 2026, 20:382,006-33
5 Oct 2026, 06:372,039-36
26 Sept 2026, 12:222,075-52
19 Sept 2026, 15:222,127no change
15 Sept 2026, 03:382,127-11
11 Sept 2026, 14:022,138-15
7 Sept 2026, 01:382,153-28
2 Sept 2026, 05:162,181-18
30 Aug 2026, 03:382,199-16
27 Aug 2026, 10:122,215-12
24 Aug 2026, 14:162,227-13
20 Aug 2026, 18:462,240-9
17 Aug 2026, 19:362,249first 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“Loot Zone™” (@lootzoner), 1,920 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/lootzoner.

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.