Telegram RegisterThe public register of Telegram
Telegram profile photo for Appkey uz | appkeyuz

Channel

Appkey uz | appkeyuz

@nimalar_bolarkin

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

1,114subscribers

-51 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-1001784771500
TypeChannel
Username@nimalar_bolarkin
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 October 2026
Last confirmed live14 November 2026
Measurements held22
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/nimalar_bolarkin

Topic

Memes & entertainment — 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 6 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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,1141,1651,139.57 August 2026 — 1,165 subscribers14 August 2026 — 1,161 subscribers17 August 2026 — 1,157 subscribers21 August 2026 — 1,156 subscribers25 August 2026 — 1,155 subscribers31 August 2026 — 1,152 subscribers3 September 2026 — 1,148 subscribers8 September 2026 — 1,145 subscribers12 September 2026 — 1,141 subscribers2 October 2026 — 1,136 subscribers6 October 2026 — 1,136 subscribers8 October 2026 — 1,130 subscribers13 October 2026 — 1,129 subscribers16 October 2026 — 1,127 subscribers19 October 2026 — 1,123 subscribers26 October 2026 — 1,122 subscribers29 October 2026 — 1,121 subscribers1 November 2026 — 1,120 subscribers3 November 2026 — 1,117 subscribers6 November 2026 — 1,114 subscribers9 November 2026 — 1,115 subscribers14 November 2026 — 1,114 subscribers7 August 202614 November 2026
22 measurements spanning 99 days, net -51. 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,106–1,173 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
14 Nov 2026, 12:051,114-1
9 Nov 2026, 16:011,115+1
6 Nov 2026, 14:401,114-3
3 Nov 2026, 21:471,117-3
1 Nov 2026, 03:051,120-1
29 Oct 2026, 12:261,121-1
26 Oct 2026, 10:591,122-1
19 Oct 2026, 23:061,123-4
16 Oct 2026, 19:581,127-2
13 Oct 2026, 21:461,129-1
8 Oct 2026, 17:171,130-6
6 Oct 2026, 03:281,136no change
2 Oct 2026, 03:381,136-5
12 Sept 2026, 07:001,141-4
8 Sept 2026, 08:361,145-3
3 Sept 2026, 09:181,148-4
31 Aug 2026, 06:031,152-3
25 Aug 2026, 02:061,155-1
21 Aug 2026, 06:051,156-1
17 Aug 2026, 20:231,157first 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Appkey uz | appkeyuz” (@nimalar_bolarkin), 1,114 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/nimalar_bolarkin.

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.