Telegram RegisterThe public register of Telegram
Telegram profile photo for 长沙COS SM 三通(有房可上门)

Channel

长沙COS SM 三通(有房可上门)

@luludawa

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

2,688subscribers

-49 since we began measuring on 16 September 2026

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

Register entry

Telegram ID-1003879632095
TypeChannel
Username@luludawa
CreatedBetween 1 February 2026 and 8 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 September 2026
Last confirmed live3 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/luludawa

Topic

Adult — 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 5 October 2026 and assigned it the closest of 31 fixed categories, at 59% 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

2,6832,7572,72016 September 2026 — 2,737 subscribers16 September 2026 — 2,737 subscribers18 September 2026 — 2,757 subscribers27 September 2026 — 2,750 subscribers5 October 2026 — 2,700 subscribers12 October 2026 — 2,683 subscribers15 October 2026 — 2,688 subscribers18 October 2026 — 2,692 subscribers22 October 2026 — 2,701 subscribers25 October 2026 — 2,699 subscribers28 October 2026 — 2,702 subscribers31 October 2026 — 2,698 subscribers3 November 2026 — 2,688 subscribers2,68816 September 20263 November 2026
13 measurements spanning 48 days, net -49. 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,672–2,768 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 17:162,688-10
31 Oct 2026, 09:462,698-4
28 Oct 2026, 04:362,702+3
25 Oct 2026, 10:312,699-2
22 Oct 2026, 03:172,701+9
18 Oct 2026, 12:152,692+4
15 Oct 2026, 07:352,688+5
12 Oct 2026, 13:572,683-17
5 Oct 2026, 12:562,700-50
27 Sept 2026, 23:372,750-7
18 Sept 2026, 13:002,757+20
16 Sept 2026, 14:262,737no change
16 Sept 2026, 14:222,737first reading

Engagement

19 posts held, back to 8 July 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 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 19 posts for this entry, the most recent from 16 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
12s
Average length
6s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

10 Sept 2026, 09:37 UTCviews —

The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

Showing the 12 most recent of 19 posts we hold for @luludawa. 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

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

Names

Channels on the register whose handles appear in this channel's posts.

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

“长沙COS SM 三通(有房可上门)” (@luludawa), 2,688 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/luludawa.

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.