Photo, posted without a caption
Signed @Dk

Channel
@LFRj6UqxC2w0MTA1
On this record: Topic · Growth · Engagement · Posts · Cite this entry
3,510subscribers
+75 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001764635825 |
|---|---|
| Type | Channel |
| Username | @LFRj6UqxC2w0MTA1 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/LFRj6UqxC2w0MTA1 |
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 88% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 03:10 | 3,510 | +1 |
| 6 Oct 2026, 21:16 | 3,509 | +2 |
| 29 Sept 2026, 17:56 | 3,507 | +5 |
| 15 Sept 2026, 18:37 | 3,502 | -6 |
| 11 Sept 2026, 18:40 | 3,508 | +3 |
| 7 Sept 2026, 14:16 | 3,505 | +25 |
| 2 Sept 2026, 16:37 | 3,480 | +19 |
| 30 Aug 2026, 09:56 | 3,461 | +16 |
| 27 Aug 2026, 12:07 | 3,445 | +12 |
| 24 Aug 2026, 09:53 | 3,433 | +16 |
| 20 Aug 2026, 07:02 | 3,417 | -3 |
| 17 Aug 2026, 13:05 | 3,420 | -6 |
| 14 Aug 2026, 13:53 | 3,426 | -4 |
| 10 Aug 2026, 23:51 | 3,430 | -6 |
| 8 Aug 2026, 01:57 | 3,436 | +1 |
| 7 Aug 2026, 15:31 | 3,435 | first reading |
20 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Photo, posted without a caption
Signed @Dk
Showing the 12 most recent of 20 posts we hold for @LFRj6UqxC2w0MTA1. 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.
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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“Dk Cnc Design Tech” (@LFRj6UqxC2w0MTA1), 3,510 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/LFRj6UqxC2w0MTA1.
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.