Telegram RegisterThe public register of Telegram
Telegram profile photo for Балашиха | Объявления

Supergroup

Балашиха | Объявления

@balashiha_adverts

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

9,230members

-362 since we began measuring on 7 August 2026

1,384 online right now

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

Register entry

Telegram ID-1001920937083
TypeSupergroup
Username@balashiha_adverts
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 August 2026
Last confirmed live21 October 2026
Measurements held20
Confirmed unchanged1 time, most recently 21 October 2026
On Telegramt.me/balashiha_adverts

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

9,2309,5929,4117 August 2026 — 9,592 members8 August 2026 — 9,590 members11 August 2026 — 9,569 members14 August 2026 — 9,549 members18 August 2026 — 9,529 members21 August 2026 — 9,505 members23 August 2026 — 9,505 members24 August 2026 — 9,485 members27 August 2026 — 9,469 members30 August 2026 — 9,457 members2 September 2026 — 9,442 members7 September 2026 — 9,417 members11 September 2026 — 9,387 members15 September 2026 — 9,375 members27 September 2026 — 9,330 members5 October 2026 — 9,299 members12 October 2026 — 9,267 members15 October 2026 — 9,249 members18 October 2026 — 9,239 members21 October 2026 — 9,230 members7 August 202621 October 2026
20 measurements spanning 75 days, net -362. 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 9,176–9,646 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
21 Oct 2026, 12:499,230-9
18 Oct 2026, 09:199,239-10
15 Oct 2026, 11:359,249-18
12 Oct 2026, 06:569,267-32
5 Oct 2026, 12:569,299-31
27 Sept 2026, 08:579,330-45
15 Sept 2026, 13:159,375-12
11 Sept 2026, 18:179,387-30
7 Sept 2026, 03:579,417-25
2 Sept 2026, 11:449,442-15
30 Aug 2026, 04:069,457-12
27 Aug 2026, 10:159,469-16
24 Aug 2026, 17:049,485-20
23 Aug 2026, 18:469,505no change
21 Aug 2026, 08:439,505-24
18 Aug 2026, 00:519,529-20
14 Aug 2026, 14:099,549-20
11 Aug 2026, 06:229,569-21
8 Aug 2026, 01:259,590-2
7 Aug 2026, 17:589,592first 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.

“Балашиха | Объявления” (@balashiha_adverts), 9,230 members as measured 21 October 2026. Telegram Register, tgregister.com/channel/balashiha_adverts.

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.