Telegram RegisterThe public register of Telegram
Telegram profile photo for Новосибирское РО ВОГ Канал

Supergroup

Новосибирское РО ВОГ Канал

@nrovog54

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

1,296members

+67 since we began measuring on 8 August 2026

83 online right now

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

Register entry

Telegram ID-1002410789492
TypeSupergroup
Username@nrovog54
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 October 2026
Last confirmed live10 October 2026
Measurements held15
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/nrovog54

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 73% 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,2291,2961,262.58 August 2026 — 1,229 members11 August 2026 — 1,232 members14 August 2026 — 1,240 members17 August 2026 — 1,243 members20 August 2026 — 1,246 members27 August 2026 — 1,251 members30 August 2026 — 1,249 members1 September 2026 — 1,244 members6 September 2026 — 1,243 members11 September 2026 — 1,246 members15 September 2026 — 1,251 members25 September 2026 — 1,263 members3 October 2026 — 1,263 members4 October 2026 — 1,279 members10 October 2026 — 1,296 members8 August 202610 October 2026
15 measurements spanning 63 days, net +67. 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,219–1,306 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
10 Oct 2026, 15:001,296+17
4 Oct 2026, 17:371,279+16
3 Oct 2026, 01:171,263no change
25 Sept 2026, 01:591,263+12
15 Sept 2026, 04:381,251+5
11 Sept 2026, 05:391,246+3
6 Sept 2026, 00:411,243-1
1 Sept 2026, 19:451,244-5
30 Aug 2026, 04:561,249-2
27 Aug 2026, 13:281,251+5
20 Aug 2026, 14:341,246+3
17 Aug 2026, 21:031,243+3
14 Aug 2026, 12:081,240+8
11 Aug 2026, 08:131,232+3
8 Aug 2026, 04:151,229first 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 10 October 2026 — this entry's latest reading, not the date you are reading this.

“Новосибирское РО ВОГ Канал” (@nrovog54), 1,296 members as measured 10 October 2026. Telegram Register, tgregister.com/channel/nrovog54.

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.