Telegram RegisterThe public register of Telegram
Telegram profile photo for 长沙会所MMK/9294公开榜

Channel

长沙会所MMK/9294公开榜

@spa0000000

Has discussion group

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

10,530subscribers

-212 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003454057171
TypeChannel
Username@spa0000000
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 August 2026
Last confirmed live28 October 2026
Measurements held45
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/spa0000000

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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

7,89310,7739,33310 August 2026 — 10,742 subscribers11 August 2026 — 10,718 subscribers12 August 2026 — 10,694 subscribers13 August 2026 — 10,677 subscribers14 August 2026 — 10,672 subscribers16 August 2026 — 10,671 subscribers17 August 2026 — 10,659 subscribers18 August 2026 — 10,643 subscribers19 August 2026 — 10,624 subscribers20 August 2026 — 10,617 subscribers21 August 2026 — 10,599 subscribers22 August 2026 — 10,599 subscribers23 August 2026 — 10,580 subscribers25 August 2026 — 10,592 subscribers25 August 2026 — 10,581 subscribers26 August 2026 — 10,569 subscribers28 August 2026 — 10,562 subscribers28 August 2026 — 10,548 subscribers30 August 2026 — 10,543 subscribers31 August 2026 — 10,574 subscribers1 September 2026 — 10,566 subscribers1 September 2026 — 9,630 subscribers6 September 2026 — 10,604 subscribers9 September 2026 — 10,196 subscribers12 September 2026 — 10,101 subscribers13 September 2026 — 9,497 subscribers18 September 2026 — 9,144 subscribers27 September 2026 — 7,893 subscribers5 October 2026 — 10,723 subscribers9 October 2026 — 10,773 subscribers13 October 2026 — 10,691 subscribers14 October 2026 — 10,677 subscribers15 October 2026 — 10,658 subscribers16 October 2026 — 10,648 subscribers17 October 2026 — 10,652 subscribers18 October 2026 — 10,649 subscribers19 October 2026 — 10,642 subscribers21 October 2026 — 10,638 subscribers22 October 2026 — 10,575 subscribers23 October 2026 — 10,568 subscribers24 October 2026 — 10,556 subscribers25 October 2026 — 10,553 subscribers26 October 2026 — 10,546 subscribers27 October 2026 — 10,535 subscribers28 October 2026 — 10,530 subscribers10,53010 August 202628 October 2026
45 measurements spanning 79 days, net -212. 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 7,461–11,205 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)SubscribersChange
28 Oct 2026, 04:0710,530-5
27 Oct 2026, 04:0710,535-11
26 Oct 2026, 02:1810,546-7
25 Oct 2026, 04:3710,553-3
24 Oct 2026, 05:5710,556-12
23 Oct 2026, 03:1710,568-7
22 Oct 2026, 04:4110,575-63
21 Oct 2026, 00:3610,638-4
19 Oct 2026, 20:1910,642-7
18 Oct 2026, 22:1810,649-3
17 Oct 2026, 21:2610,652+4
16 Oct 2026, 18:5010,648-10
15 Oct 2026, 21:3810,658-19
14 Oct 2026, 20:5510,677-14
13 Oct 2026, 13:2810,691-82
9 Oct 2026, 16:5910,773+50
5 Oct 2026, 08:5710,723+2,830
27 Sept 2026, 05:577,893-1,251
18 Sept 2026, 02:179,144-353
13 Sept 2026, 17:419,497first reading

Engagement

No public post preview. We read this entry on 22 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

Named by 2 registered channels — 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.

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

“长沙会所MMK/9294公开榜” (@spa0000000), 10,530 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/spa0000000.

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.