Telegram RegisterThe public register of Telegram
Telegram profile photo for disruption98

Channel

disruption98

@disruption_98

Has discussion group

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

2,167subscribers

-70 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-1001142859571
TypeChannel
Username@disruption_98
CreatedBetween 1 April 2016 and 30 November 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 September 2026
Last confirmed live11 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/disruption_98

Topic

Other / unclassifiable — 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 18 September 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 why it has no browse page of its own yet.

Growth

2,1672,2372,2027 August 2026 — 2,237 subscribers7 August 2026 — 2,236 subscribers10 August 2026 — 2,227 subscribers13 August 2026 — 2,217 subscribers16 August 2026 — 2,213 subscribers20 August 2026 — 2,214 subscribers23 August 2026 — 2,215 subscribers29 August 2026 — 2,217 subscribers2 September 2026 — 2,215 subscribers6 September 2026 — 2,207 subscribers11 September 2026 — 2,208 subscribers15 September 2026 — 2,207 subscribers18 September 2026 — 2,207 subscribers25 September 2026 — 2,184 subscribers4 October 2026 — 2,171 subscribers11 October 2026 — 2,167 subscribers7 August 202611 October 2026
16 measurements spanning 64 days, net -70. 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,157–2,248 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 03:422,167-4
4 Oct 2026, 20:402,171-13
25 Sept 2026, 13:162,184-23
18 Sept 2026, 15:292,207no change
15 Sept 2026, 07:582,207-1
11 Sept 2026, 06:572,208+1
6 Sept 2026, 21:412,207-8
2 Sept 2026, 09:032,215-2
29 Aug 2026, 23:282,217+2
23 Aug 2026, 22:352,215+1
20 Aug 2026, 02:422,214+1
16 Aug 2026, 21:242,213-4
13 Aug 2026, 05:562,217-10
10 Aug 2026, 09:442,227-9
7 Aug 2026, 17:142,236-1
7 Aug 2026, 16:142,237first 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 11 October 2026 — this entry's latest reading, not the date you are reading this.

“disruption98” (@disruption_98), 2,167 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/disruption_98.

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.