Telegram RegisterThe public register of Telegram
Telegram profile photo for DJ KIRPICH

Channel

DJ KIRPICH

@DJKIRPICH

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

165subscribers

+22 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002017300697
TypeChannel
Username@DJKIRPICH
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 October 2026
Last confirmed live26 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/DJKIRPICH

Topic

Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 17 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

1431651548 August 2026 — 143 subscribers17 August 2026 — 146 subscribers24 August 2026 — 147 subscribers9 September 2026 — 148 subscribers17 September 2026 — 155 subscribers2 October 2026 — 157 subscribers12 October 2026 — 160 subscribers17 October 2026 — 160 subscribers19 October 2026 — 161 subscribers26 October 2026 — 165 subscribers8 August 202626 October 2026
10 measurements spanning 79 days, net +22. 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 140–168 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Oct 2026, 21:14165+4
19 Oct 2026, 04:18161+1
17 Oct 2026, 05:07160no change
12 Oct 2026, 20:40160+3
2 Oct 2026, 15:19157+2
17 Sept 2026, 04:15155+7
9 Sept 2026, 04:00148+1
24 Aug 2026, 04:48147+1
17 Aug 2026, 09:28146+3
8 Aug 2026, 22:45143first 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.

Mentions

Named by 3 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 26 October 2026 — this entry's latest reading, not the date you are reading this.

“DJ KIRPICH” (@DJKIRPICH), 165 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/DJKIRPICH.

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.