Telegram RegisterThe public register of Telegram
Telegram profile photo for Optimus Medicus Chat

Supergroup

Optimus Medicus Chat

@MedicusChat

Has discussion group

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

5,877members

-132 since we began measuring on 7 August 2026

486 online right now

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

Register entry

Telegram ID-1002196392881
TypeSupergroup
Username@MedicusChat
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live2 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/MedicusChat

Topic

Health & wellness — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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

5,8776,0095,9437 August 2026 — 6,009 members8 August 2026 — 6,006 members11 August 2026 — 6,003 members17 August 2026 — 6,002 members20 August 2026 — 5,998 members24 August 2026 — 5,996 members27 August 2026 — 5,986 members29 August 2026 — 5,986 members30 August 2026 — 5,978 members2 September 2026 — 5,977 members6 September 2026 — 5,961 members11 September 2026 — 5,951 members14 September 2026 — 5,946 members18 September 2026 — 5,941 members28 September 2026 — 5,930 members5 October 2026 — 5,919 members12 October 2026 — 5,916 members15 October 2026 — 5,915 members17 October 2026 — 5,912 members21 October 2026 — 5,904 members23 October 2026 — 5,903 members27 October 2026 — 5,896 members30 October 2026 — 5,882 members2 November 2026 — 5,877 members7 August 20262 November 2026
24 measurements spanning 87 days, net -132. 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 5,857–6,029 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
2 Nov 2026, 12:595,877-5
30 Oct 2026, 03:355,882-14
27 Oct 2026, 07:365,896-7
23 Oct 2026, 20:465,903-1
21 Oct 2026, 03:405,904-8
17 Oct 2026, 23:185,912-3
15 Oct 2026, 05:185,915-1
12 Oct 2026, 13:015,916-3
5 Oct 2026, 21:545,919-11
28 Sept 2026, 09:025,930-11
18 Sept 2026, 16:185,941-5
14 Sept 2026, 16:195,946-5
11 Sept 2026, 12:015,951-10
6 Sept 2026, 23:395,961-16
2 Sept 2026, 07:165,977-1
30 Aug 2026, 13:285,978-8
29 Aug 2026, 21:145,986no change
27 Aug 2026, 15:255,986-10
24 Aug 2026, 11:345,996-2
20 Aug 2026, 13:025,998first 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.

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

“Optimus Medicus Chat” (@MedicusChat), 5,877 members as measured 2 November 2026. Telegram Register, tgregister.com/channel/MedicusChat.

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.