Telegram RegisterThe public register of Telegram
Telegram profile photo for Nishon-mark Ов гуруҳи!

Supergroup

Nishon-mark Ов гуруҳи!

@nishon_mark_ohota

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

3,537members

+304 since we began measuring on 7 August 2026

805 online right now

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

Register entry

Telegram ID-1003752140572
TypeSupergroup
Username@nishon_mark_ohota
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 September 2026
Last confirmed live19 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/nishon_mark_ohota

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 14 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

3,2303,5373,383.57 August 2026 — 3,233 members8 August 2026 — 3,230 members11 August 2026 — 3,252 members14 August 2026 — 3,281 members17 August 2026 — 3,301 members20 August 2026 — 3,312 members24 August 2026 — 3,344 members27 August 2026 — 3,365 members30 August 2026 — 3,362 members2 September 2026 — 3,366 members7 September 2026 — 3,435 members8 September 2026 — 3,435 members11 September 2026 — 3,489 members15 September 2026 — 3,506 members19 September 2026 — 3,537 members7 August 202619 September 2026
15 measurements spanning 43 days, net +304. 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 3,184–3,583 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
19 Sept 2026, 17:573,537+31
15 Sept 2026, 12:593,506+17
11 Sept 2026, 21:183,489+54
8 Sept 2026, 20:473,435no change
7 Sept 2026, 09:563,435+69
2 Sept 2026, 20:543,366+4
30 Aug 2026, 12:433,362-3
27 Aug 2026, 19:183,365+21
24 Aug 2026, 09:383,344+32
20 Aug 2026, 09:383,312+11
17 Aug 2026, 13:353,301+20
14 Aug 2026, 03:483,281+29
11 Aug 2026, 04:433,252+22
8 Aug 2026, 05:113,230-3
7 Aug 2026, 19:433,233first 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“Nishon-mark Ов гуруҳи!” (@nishon_mark_ohota), 3,537 members as measured 19 September 2026. Telegram Register, tgregister.com/channel/nishon_mark_ohota.

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.