Telegram RegisterThe public register of Telegram
Telegram profile photo for Волонтеры Мюнхен

Supergroup

Волонтеры Мюнхен

@mucvlntrs

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

2,281members

+27 since we began measuring on 7 August 2026

426 online right now

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

Register entry

Telegram ID-1001523430234
TypeSupergroup
Username@mucvlntrs
DescriptionПравила группы: https://t.me/mucvlntrs/85050 Связь с администрацией группы: @vol_muc_contact_bot
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 September 2026
Last confirmed live17 September 2026
Measurements held14
On Telegramt.me/mucvlntrs

Topic

Local community — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

2,2542,2882,2717 August 2026 — 2,254 members8 August 2026 — 2,257 members10 August 2026 — 2,263 members17 August 2026 — 2,262 members20 August 2026 — 2,280 members24 August 2026 — 2,282 members27 August 2026 — 2,288 members29 August 2026 — 2,282 members1 September 2026 — 2,285 members4 September 2026 — 2,271 members10 September 2026 — 2,272 members13 September 2026 — 2,273 members17 September 2026 — 2,281 members17 September 2026 — 2,281 members2,2817 August 202617 September 2026
14 measurements spanning 41 days, net +27. 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,249–2,293 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
17 Sept 2026, 22:442,281no change
17 Sept 2026, 14:412,281+8
13 Sept 2026, 21:022,273+1
10 Sept 2026, 04:192,272+1
4 Sept 2026, 23:372,271-14
1 Sept 2026, 15:172,285+3
29 Aug 2026, 22:042,282-6
27 Aug 2026, 06:362,288+6
24 Aug 2026, 04:262,282+2
20 Aug 2026, 23:052,280+18
17 Aug 2026, 12:432,262-1
10 Aug 2026, 21:582,263+6
8 Aug 2026, 03:272,257+3
7 Aug 2026, 13:162,254first 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Волонтеры Мюнхен” (@mucvlntrs), 2,281 members as measured 17 September 2026. Telegram Register, tgregister.com/channel/mucvlntrs.

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.