Telegram RegisterThe public register of Telegram
Telegram profile photo for 03 ОБЪЯВЛЕНИЯ ИВОЛГИНСКОГО РАЙОНА

Supergroup

03 ОБЪЯВЛЕНИЯ ИВОЛГИНСКОГО РАЙОНА

@ivolginsk_03

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

5,302members

-96 since we began measuring on 8 August 2026

12 online right now

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

Register entry

Telegram ID-1001920613567
TypeSupergroup
Username@ivolginsk_03
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live15 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/ivolginsk_03

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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

5,3025,3985,3508 August 2026 — 5,398 members8 August 2026 — 5,393 members12 August 2026 — 5,386 members15 August 2026 — 5,380 members18 August 2026 — 5,367 members21 August 2026 — 5,362 members25 August 2026 — 5,353 members27 August 2026 — 5,350 members30 August 2026 — 5,342 members31 August 2026 — 5,342 members3 September 2026 — 5,326 members8 September 2026 — 5,312 members12 September 2026 — 5,305 members15 September 2026 — 5,302 members8 August 202615 September 2026
14 measurements spanning 39 days, net -96. 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,288–5,412 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
15 Sept 2026, 20:185,302-3
12 Sept 2026, 10:015,305-7
8 Sept 2026, 10:185,312-14
3 Sept 2026, 10:175,326-16
31 Aug 2026, 18:545,342no change
30 Aug 2026, 20:125,342-8
27 Aug 2026, 16:195,350-3
25 Aug 2026, 02:495,353-9
21 Aug 2026, 19:385,362-5
18 Aug 2026, 09:545,367-13
15 Aug 2026, 05:145,380-6
12 Aug 2026, 06:555,386-7
8 Aug 2026, 23:525,393-5
8 Aug 2026, 00:165,398first 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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“03 ОБЪЯВЛЕНИЯ ИВОЛГИНСКОГО РАЙОНА” (@ivolginsk_03), 5,302 members as measured 15 September 2026. Telegram Register, tgregister.com/channel/ivolginsk_03.

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.