Telegram RegisterThe public register of Telegram
Telegram profile photo for Абхазские проекты

Channel

Абхазские проекты

@abkhazproject

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

1,027subscribers

-13 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001142149526
TypeChannel
Username@abkhazproject
Created16 August 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 October 2026
Last confirmed live16 November 2026
Measurements held17
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/abkhazproject

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 8 October 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 the other topics.

Growth

1,0271,0401,033.57 August 2026 — 1,040 subscribers11 August 2026 — 1,039 subscribers14 August 2026 — 1,038 subscribers17 August 2026 — 1,037 subscribers20 August 2026 — 1,036 subscribers23 August 2026 — 1,033 subscribers26 August 2026 — 1,032 subscribers29 August 2026 — 1,033 subscribers11 September 2026 — 1,032 subscribers28 September 2026 — 1,031 subscribers8 October 2026 — 1,031 subscribers19 October 2026 — 1,030 subscribers31 October 2026 — 1,031 subscribers4 November 2026 — 1,032 subscribers6 November 2026 — 1,029 subscribers10 November 2026 — 1,028 subscribers16 November 2026 — 1,027 subscribers7 August 202616 November 2026
17 measurements spanning 101 days, net -13. 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,025–1,042 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 10:111,027-1
10 Nov 2026, 15:551,028-1
6 Nov 2026, 21:191,029-3
4 Nov 2026, 03:011,032+1
31 Oct 2026, 16:001,031+1
19 Oct 2026, 06:181,030-1
8 Oct 2026, 18:201,031no change
28 Sept 2026, 07:421,031-1
11 Sept 2026, 07:171,032-1
29 Aug 2026, 17:331,033+1
26 Aug 2026, 11:061,032-1
23 Aug 2026, 19:391,033-3
20 Aug 2026, 10:471,036-1
17 Aug 2026, 12:161,037-1
14 Aug 2026, 12:551,038-1
11 Aug 2026, 08:441,039-1
7 Aug 2026, 04:031,040first 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

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

“Абхазские проекты” (@abkhazproject), 1,027 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/abkhazproject.

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.