Telegram RegisterThe public register of Telegram
Telegram profile photo for AVTO "Baraholka"

Supergroup

AVTO "Baraholka"

@auto_pokupka

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

1,429members

+21 since we began measuring on 6 August 2026

116 online right now

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

Register entry

Telegram ID-1001172481518
TypeSupergroup
Username@auto_pokupka
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 September 2026
Last confirmed live7 October 2026
Measurements held15
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/auto_pokupka

Topic

Automotive — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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,4031,4451,4246 August 2026 — 1,408 members6 August 2026 — 1,403 members10 August 2026 — 1,418 members13 August 2026 — 1,411 members16 August 2026 — 1,423 members19 August 2026 — 1,426 members22 August 2026 — 1,438 members28 August 2026 — 1,439 members31 August 2026 — 1,436 members8 September 2026 — 1,435 members12 September 2026 — 1,445 members16 September 2026 — 1,434 members29 September 2026 — 1,434 members30 September 2026 — 1,425 members7 October 2026 — 1,429 members1,4296 August 20267 October 2026
15 measurements spanning 62 days, net +21. 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,397–1,451 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
7 Oct 2026, 20:401,429+4
30 Sept 2026, 19:381,425-9
29 Sept 2026, 03:261,434no change
16 Sept 2026, 02:181,434-11
12 Sept 2026, 17:391,445+10
8 Sept 2026, 22:171,435-1
31 Aug 2026, 14:241,436-3
28 Aug 2026, 03:461,439+1
22 Aug 2026, 21:341,438+12
19 Aug 2026, 19:131,426+3
16 Aug 2026, 21:231,423+12
13 Aug 2026, 13:341,411-7
10 Aug 2026, 07:161,418+15
6 Aug 2026, 23:401,403-5
6 Aug 2026, 12:081,408first 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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“AVTO "Baraholka"” (@auto_pokupka), 1,429 members as measured 7 October 2026. Telegram Register, tgregister.com/channel/auto_pokupka.

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.