Telegram RegisterThe public register of Telegram
Telegram profile photo for LK Dark to Light

Channel

LK Dark to Light

@LKDarktoLight

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

3,350subscribers

-81 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001405782560
TypeChannel
Username@LKDarktoLight
Created15 January 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/LKDarktoLight

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 14 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

3,3503,4313,390.56 August 2026 — 3,431 subscribers6 August 2026 — 3,431 subscribers9 August 2026 — 3,427 subscribers12 August 2026 — 3,420 subscribers16 August 2026 — 3,415 subscribers19 August 2026 — 3,411 subscribers22 August 2026 — 3,403 subscribers25 August 2026 — 3,401 subscribers28 August 2026 — 3,390 subscribers31 August 2026 — 3,388 subscribers4 September 2026 — 3,387 subscribers10 September 2026 — 3,366 subscribers13 September 2026 — 3,357 subscribers17 September 2026 — 3,350 subscribers6 August 202617 September 2026
14 measurements spanning 42 days, net -81. 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 3,338–3,443 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 20:383,350-7
13 Sept 2026, 17:173,357-9
10 Sept 2026, 01:183,366-21
4 Sept 2026, 09:383,387-1
31 Aug 2026, 15:233,388-2
28 Aug 2026, 21:373,390-11
25 Aug 2026, 14:443,401-2
22 Aug 2026, 18:563,403-8
19 Aug 2026, 03:513,411-4
16 Aug 2026, 05:523,415-5
12 Aug 2026, 12:063,420-7
9 Aug 2026, 03:013,427-4
6 Aug 2026, 10:513,431no change
6 Aug 2026, 09:513,431first reading

Engagement

20 posts held, back to 21 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 December 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Dec 2025, 18:13 UTC908 viewsread 7 August 2026

https://fixupx.com/gem_comms/status/1998093345554567440?s=67

Signed Q’d Up

6 Dec 2025, 09:20 UTC≈1,050 viewsread 7 August 2026

https://fixupx.com/gem_comms/status/1997221927472320585?s=67

Signed Q’d Up

6 Dec 2025, 07:13 UTC672 viewsread 7 August 2026

https://fixupx.com/gem_comms/status/1997202557660282992?s=67

Signed Q’d Up

3 Dec 2025, 20:55 UTC534 viewsread 7 August 2026

https://fixupx.com/gem_comms/status/1996317618169405494?s=67

Signed Q’d Up

2 Dec 2025, 17:04 UTC538 viewsread 7 August 2026

https://fixupx.com/gem_comms/status/1994840316588036543?s=67

Signed Q’d Up

2 Dec 2025, 17:03 UTCviews —

LK Dark to Light pinned «https://fixupx.com/gem_comms/status/1992955243991359639?s=67»

29 Nov 2025, 23:19 UTC546 viewsread 7 August 2026

https://fixupx.com/gem_comms/status/1994899648977207713?s=67

Signed Q’d Up

29 Nov 2025, 21:28 UTC354 viewsread 7 August 2026

https://fixupx.com/gem_comms/status/1994878908898910297?s=52&t=-DiYAZJSOzIe174XbgSTNg

Signed Q’d Up

29 Nov 2025, 18:46 UTC374 viewsread 7 August 2026

https://fixupx.com/gem_comms/status/1994840316588036543?s=52&t=-DiYAZJSOzIe174XbgSTNg

Signed Q’d Up

28 Nov 2025, 13:07 UTC417 viewsread 7 August 2026

https://fixupx.com/gem_comms/status/1994392311028129990?s=67

Signed Q’d Up

Showing the 12 most recent of 20 posts we hold for @LKDarktoLight. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“LK Dark to Light” (@LKDarktoLight), 3,350 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/LKDarktoLight.

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.