Telegram RegisterThe public register of Telegram
Telegram profile photo for MVRS Token Chat

Supergroup

MVRS Token Chat

@mvrstokencommunity

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

1,066members

-60 since we began measuring on 7 August 2026

16 online right now

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

Register entry

Telegram ID-1001748220952
TypeSupergroup
Username@mvrstokencommunity
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 October 2026
Last confirmed live12 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/mvrstokencommunity

Topic

Crypto & trading — 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 7 October 2026 and assigned it the closest of 31 fixed categories, at 87% 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

1,0661,1261,0967 August 2026 — 1,126 members10 August 2026 — 1,123 members13 August 2026 — 1,118 members17 August 2026 — 1,115 members20 August 2026 — 1,113 members24 August 2026 — 1,111 members27 August 2026 — 1,107 members29 August 2026 — 1,099 members5 September 2026 — 1,094 members10 September 2026 — 1,089 members14 September 2026 — 1,084 members18 September 2026 — 1,082 members27 September 2026 — 1,075 members5 October 2026 — 1,069 members7 October 2026 — 1,069 members12 October 2026 — 1,066 members7 August 202612 October 2026
16 measurements spanning 66 days, net -60. 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 1,057–1,135 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
12 Oct 2026, 08:561,066-3
7 Oct 2026, 18:081,069no change
5 Oct 2026, 12:381,069-6
27 Sept 2026, 20:161,075-7
18 Sept 2026, 17:181,082-2
14 Sept 2026, 04:381,084-5
10 Sept 2026, 18:361,089-5
5 Sept 2026, 18:181,094-5
29 Aug 2026, 23:251,099-8
27 Aug 2026, 09:421,107-4
24 Aug 2026, 01:381,111-2
20 Aug 2026, 15:351,113-2
17 Aug 2026, 11:531,115-3
13 Aug 2026, 17:161,118-5
10 Aug 2026, 07:231,123-3
7 Aug 2026, 04:071,126first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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

“MVRS Token Chat” (@mvrstokencommunity), 1,066 members as measured 12 October 2026. Telegram Register, tgregister.com/channel/mvrstokencommunity.

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.