Telegram RegisterThe public register of Telegram
Telegram profile photo for MMSH LOGISTIC LUX мчж

Supergroup

MMSH LOGISTIC LUX мчж

@mmshlogisticlux

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

9,342members

+77 since we began measuring on 7 August 2026

217 online right now

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

Register entry

Telegram ID-1001519806920
TypeSupergroup
Username@mmshlogisticlux
CreatedBetween 1 August 2021 and 31 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 August 2026
Last confirmed live17 October 2026
Measurements held20
Confirmed unchanged1 time, most recently 17 October 2026
On Telegramt.me/mmshlogisticlux

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 99% 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

9,1009,3539,226.57 August 2026 — 9,265 members8 August 2026 — 9,260 members10 August 2026 — 9,240 members13 August 2026 — 9,223 members16 August 2026 — 9,222 members19 August 2026 — 9,223 members23 August 2026 — 9,173 members23 August 2026 — 9,173 members26 August 2026 — 9,132 members29 August 2026 — 9,125 members1 September 2026 — 9,100 members5 September 2026 — 9,150 members10 September 2026 — 9,201 members14 September 2026 — 9,232 members18 September 2026 — 9,256 members27 September 2026 — 9,317 members5 October 2026 — 9,318 members12 October 2026 — 9,328 members15 October 2026 — 9,353 members17 October 2026 — 9,342 members9,3427 August 202617 October 2026
20 measurements spanning 71 days, net +77. 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 9,062–9,391 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
17 Oct 2026, 19:279,342-11
15 Oct 2026, 05:259,353+25
12 Oct 2026, 03:149,328+10
5 Oct 2026, 10:219,318+1
27 Sept 2026, 00:589,317+61
18 Sept 2026, 02:029,256+24
14 Sept 2026, 02:569,232+31
10 Sept 2026, 10:029,201+51
5 Sept 2026, 06:389,150+50
1 Sept 2026, 02:579,100-25
29 Aug 2026, 12:569,125-7
26 Aug 2026, 03:169,132-41
23 Aug 2026, 21:389,173no change
23 Aug 2026, 10:189,173-50
19 Aug 2026, 12:569,223+1
16 Aug 2026, 19:039,222-1
13 Aug 2026, 13:089,223-17
10 Aug 2026, 21:079,240-20
8 Aug 2026, 07:489,260-5
7 Aug 2026, 18:489,265first reading

Engagement

No public post preview. We read this entry on 24 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.

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

“MMSH LOGISTIC LUX мчж” (@mmshlogisticlux), 9,342 members as measured 17 October 2026. Telegram Register, tgregister.com/channel/mmshlogisticlux.

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.