Telegram RegisterThe public register of Telegram
Telegram profile photo for @lumtn

Channel

@lumtn

@lumtn

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

6subscribers

-1 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002147392647
TypeChannel
Username@lumtn
Created12 September 2024 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live27 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 27 October 2026
On Telegramt.me/lumtn

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 4 October 2026 and assigned it the closest of 31 fixed categories, at 49% 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

68711 August 2026 — 7 subscribers12 August 2026 — 7 subscribers4 October 2026 — 8 subscribers27 October 2026 — 6 subscribers11 August 202627 October 2026
4 measurements spanning 77 days, net -1. 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 6–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Oct 2026, 16:406-2
4 Oct 2026, 08:398+1
12 Aug 2026, 17:017no change
11 Aug 2026, 06:497first reading

Engagement

11 posts held, back to 12 September 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 11 posts for this entry, the most recent from 11 October 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

11 Oct 2024, 08:57 UTC≈1,000 viewsread 12 August 2026

‌ ‌ And when I'm back in chicago , just trust me you ’ll be fine

Showing the 11 most recent of 11 posts we hold for @lumtn. 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.

Mentions

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

“@lumtn” (@lumtn), 6 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/lumtn.

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.