Telegram RegisterThe public register of Telegram
Telegram profile photo for PIRUK

Channel

PIRUK

@PIRUK_Music

Has discussion group

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

1,619subscribers

+194 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-1003657527514
TypeChannel
Username@PIRUK_Music
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 September 2026
Last confirmed live16 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/PIRUK_Music

Topic

Music — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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,4221,6301,5267 August 2026 — 1,425 subscribers8 August 2026 — 1,423 subscribers11 August 2026 — 1,422 subscribers15 August 2026 — 1,423 subscribers17 August 2026 — 1,428 subscribers23 August 2026 — 1,431 subscribers26 August 2026 — 1,428 subscribers29 August 2026 — 1,458 subscribers1 September 2026 — 1,466 subscribers6 September 2026 — 1,452 subscribers11 September 2026 — 1,442 subscribers15 September 2026 — 1,435 subscribers19 September 2026 — 1,428 subscribers29 September 2026 — 1,460 subscribers29 September 2026 — 1,460 subscribers6 October 2026 — 1,609 subscribers13 October 2026 — 1,625 subscribers16 October 2026 — 1,627 subscribers22 October 2026 — 1,628 subscribers25 October 2026 — 1,630 subscribers29 October 2026 — 1,626 subscribers1 November 2026 — 1,620 subscribers3 November 2026 — 1,617 subscribers11 November 2026 — 1,616 subscribers16 November 2026 — 1,619 subscribers1,6197 August 202616 November 2026
25 measurements spanning 101 days, net +194. 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,391–1,661 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
16 Nov 2026, 15:361,619+3
11 Nov 2026, 02:301,616-1
3 Nov 2026, 23:511,617-3
1 Nov 2026, 08:501,620-6
29 Oct 2026, 00:361,626-4
25 Oct 2026, 16:271,630+2
22 Oct 2026, 16:481,628+1
16 Oct 2026, 05:361,627+2
13 Oct 2026, 04:271,625+16
6 Oct 2026, 11:351,609+149
29 Sept 2026, 02:021,460no change
29 Sept 2026, 01:011,460+32
19 Sept 2026, 09:391,428-7
15 Sept 2026, 02:411,435-7
11 Sept 2026, 06:001,442-10
6 Sept 2026, 06:211,452-14
1 Sept 2026, 19:061,466+8
29 Aug 2026, 11:251,458+30
26 Aug 2026, 15:231,428-3
23 Aug 2026, 22:051,431first 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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“PIRUK” (@PIRUK_Music), 1,619 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/PIRUK_Music.

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.