Telegram RegisterThe public register of Telegram
Telegram profile photo for ОМСК ОБЪЯВЛЕНИЯ

Supergroup

ОМСК ОБЪЯВЛЕНИЯ

@bigomsk

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

9,230members

+492 since we began measuring on 7 August 2026

1,030 online right now

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

Register entry

Telegram ID-1002326446491
TypeSupergroup
Username@bigomsk
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 August 2026
Last confirmed live21 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 21 October 2026
On Telegramt.me/bigomsk

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

8,7389,2308,9847 August 2026 — 8,738 members8 August 2026 — 8,743 members10 August 2026 — 8,770 members13 August 2026 — 8,791 members16 August 2026 — 8,783 members20 August 2026 — 8,812 members24 August 2026 — 8,841 members24 August 2026 — 8,841 members26 August 2026 — 8,863 members30 August 2026 — 8,926 members1 September 2026 — 8,929 members6 September 2026 — 8,962 members11 September 2026 — 8,942 members14 September 2026 — 8,926 members18 September 2026 — 8,988 members28 September 2026 — 9,088 members6 October 2026 — 9,166 members12 October 2026 — 9,207 members15 October 2026 — 9,199 members18 October 2026 — 9,220 members21 October 2026 — 9,230 members7 August 202621 October 2026
21 measurements spanning 75 days, net +492. 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 8,664–9,304 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 21
Measured (UTC)MembersChange
21 Oct 2026, 11:169,230+10
18 Oct 2026, 09:489,220+21
15 Oct 2026, 12:389,199-8
12 Oct 2026, 15:579,207+41
6 Oct 2026, 02:569,166+78
28 Sept 2026, 11:169,088+100
18 Sept 2026, 19:198,988+62
14 Sept 2026, 08:558,926-16
11 Sept 2026, 00:188,942-20
6 Sept 2026, 03:578,962+33
1 Sept 2026, 23:348,929+3
30 Aug 2026, 05:438,926+63
26 Aug 2026, 22:548,863+22
24 Aug 2026, 11:418,841no change
24 Aug 2026, 05:528,841+29
20 Aug 2026, 03:058,812+29
16 Aug 2026, 21:238,783-8
13 Aug 2026, 11:268,791+21
10 Aug 2026, 19:118,770+27
8 Aug 2026, 02:478,743first 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 21 October 2026 — this entry's latest reading, not the date you are reading this.

“ОМСК ОБЪЯВЛЕНИЯ” (@bigomsk), 9,230 members as measured 21 October 2026. Telegram Register, tgregister.com/channel/bigomsk.

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.