Telegram RegisterThe public register of Telegram
Telegram profile photo for АВИТО [КАВКАЗ]

Supergroup

АВИТО [КАВКАЗ]

@avit0_kavkaz

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

1,614members

+53 since we began measuring on 7 August 2026

100 online right now

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

Register entry

Telegram ID-1002301687451
TypeSupergroup
Username@avit0_kavkaz
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live16 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/avit0_kavkaz

Topic

Marketing & affiliate — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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 the other topics.

Growth

1,5571,6141,585.57 August 2026 — 1,561 members11 August 2026 — 1,557 members13 August 2026 — 1,558 members16 August 2026 — 1,592 members20 August 2026 — 1,583 members23 August 2026 — 1,594 members28 August 2026 — 1,590 members31 August 2026 — 1,592 members3 September 2026 — 1,584 members8 September 2026 — 1,569 members13 September 2026 — 1,568 members17 September 2026 — 1,569 members26 September 2026 — 1,566 members27 September 2026 — 1,566 members11 October 2026 — 1,581 members14 October 2026 — 1,571 members17 October 2026 — 1,567 members21 October 2026 — 1,566 members23 October 2026 — 1,569 members27 October 2026 — 1,563 members30 October 2026 — 1,559 members2 November 2026 — 1,563 members8 November 2026 — 1,575 members11 November 2026 — 1,580 members16 November 2026 — 1,614 members7 August 202616 November 2026
25 measurements spanning 101 days, net +53. 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,548–1,623 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
16 Nov 2026, 20:461,614+34
11 Nov 2026, 22:061,580+5
8 Nov 2026, 07:491,575+12
2 Nov 2026, 03:141,563+4
30 Oct 2026, 12:101,559-4
27 Oct 2026, 04:271,563-6
23 Oct 2026, 19:271,569+3
21 Oct 2026, 01:001,566-1
17 Oct 2026, 18:181,567-4
14 Oct 2026, 14:511,571-10
11 Oct 2026, 00:211,581+15
27 Sept 2026, 00:221,566no change
26 Sept 2026, 08:001,566-3
17 Sept 2026, 03:411,569+1
13 Sept 2026, 01:181,568-1
8 Sept 2026, 18:591,569-15
3 Sept 2026, 17:421,584-8
31 Aug 2026, 18:241,592+2
28 Aug 2026, 20:361,590-4
23 Aug 2026, 14:141,594first 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.

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“АВИТО [КАВКАЗ]” (@avit0_kavkaz), 1,614 members as measured 16 November 2026. Telegram Register, tgregister.com/channel/avit0_kavkaz.

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.