Telegram RegisterThe public register of Telegram
Telegram profile photo for Kaj exchange

Channel

Kaj exchange

@kajexchangeofficial

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

2,232subscribers

+66 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001076280378
TypeChannel
Username@kajexchangeofficial
CreatedBetween 1 September 2016 and 30 September 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live29 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/kajexchangeofficial

Growth

2,1642,2322,1986 August 2026 — 2,166 subscribers6 August 2026 — 2,166 subscribers9 August 2026 — 2,164 subscribers16 August 2026 — 2,170 subscribers19 August 2026 — 2,171 subscribers23 August 2026 — 2,170 subscribers26 August 2026 — 2,230 subscribers29 August 2026 — 2,232 subscribers6 August 202629 August 2026
8 measurements spanning 24 days, net +66. 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 2,154–2,242 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 20:472,232+2
26 Aug 2026, 13:072,230+60
23 Aug 2026, 07:242,170-1
19 Aug 2026, 10:142,171+1
16 Aug 2026, 15:572,170+6
9 Aug 2026, 21:122,164-2
6 Aug 2026, 06:062,166no change
6 Aug 2026, 00:572,166first reading

Engagement

20 posts held, back to 14 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 23 December 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

23 Dec 2025, 11:45 UTC832 views0 reactionsread 7 August 2026
Photo

⭕️ نرخ حواله امروز سه‌شنبه ۲ دی

22 Dec 2025, 11:40 UTC490 viewsread 7 August 2026
Photo

⭕️ نرخ حواله امروز دوشنبه ۱ دی

21 Dec 2025, 09:59 UTC338 viewsread 7 August 2026
Photo

⭕️ نرخ حواله امروز یکشنبه ۳۰ آذر

21 Dec 2025, 09:59 UTC295 viewsread 7 August 2026
Photo

⭕️ نرخ ارز امروز یکشنبه ۳۰ آذر

20 Dec 2025, 11:07 UTC270 viewsread 7 August 2026
Photo

⭕️ نرخ حواله امروز شنبه ۲۹ آذر

17 Dec 2025, 11:25 UTC353 viewsread 7 August 2026
Photo

⭕️ نرخ حواله امروز چهارشنبه ۲۶ آذر

17 Dec 2025, 11:25 UTC341 viewsread 7 August 2026
Photo

⭕️ نرخ دلار امروز چهارشنبه ۲۶ آذر

Showing the 12 most recent of 20 posts we hold for @kajexchangeofficial. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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

“Kaj exchange” (@kajexchangeofficial), 2,232 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/kajexchangeofficial.

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.