Telegram RegisterThe public register of Telegram
Telegram profile photo for EXCHANGE KIEV

Channel

EXCHANGE KIEV

@fortex_exchange_kiev

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

3,686subscribers

-29 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001765837385
TypeChannel
Username@fortex_exchange_kiev
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/fortex_exchange_kiev

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

3,6813,7213,7016 August 2026 — 3,715 subscribers6 August 2026 — 3,716 subscribers9 August 2026 — 3,717 subscribers12 August 2026 — 3,721 subscribers15 August 2026 — 3,716 subscribers18 August 2026 — 3,712 subscribers21 August 2026 — 3,709 subscribers24 August 2026 — 3,706 subscribers28 August 2026 — 3,703 subscribers31 August 2026 — 3,706 subscribers4 September 2026 — 3,704 subscribers10 September 2026 — 3,696 subscribers13 September 2026 — 3,695 subscribers17 September 2026 — 3,692 subscribers27 September 2026 — 3,687 subscribers5 October 2026 — 3,681 subscribers11 October 2026 — 3,686 subscribers3,6866 August 202611 October 2026
17 measurements spanning 66 days, net -29. 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 3,675–3,727 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 13:163,686+5
5 Oct 2026, 09:563,681-6
27 Sept 2026, 03:373,687-5
17 Sept 2026, 18:153,692-3
13 Sept 2026, 17:373,695-1
10 Sept 2026, 00:383,696-8
4 Sept 2026, 14:193,704-2
31 Aug 2026, 16:133,706+3
28 Aug 2026, 06:233,703-3
24 Aug 2026, 23:233,706-3
21 Aug 2026, 19:153,709-3
18 Aug 2026, 18:223,712-4
15 Aug 2026, 19:573,716-5
12 Aug 2026, 04:383,721+4
9 Aug 2026, 06:123,717+1
6 Aug 2026, 16:503,716+1
6 Aug 2026, 07:163,715first reading

Engagement

30 posts held, back to 31 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pages of 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 30 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 11:59 UTC525 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,66 / 44,75 🇪🇺/🇺🇦EUR: 51,52 / 51,72 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

7 Aug 2026, 11:32 UTC560 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,65 / 44,75 🇪🇺/🇺🇦EUR: 51,50 / 51,70 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

7 Aug 2026, 10:25 UTC608 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,63 / 44,73 🇪🇺/🇺🇦EUR: 51,45 / 51,65 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

7 Aug 2026, 08:48 UTC635 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,62 / 44,72 🇪🇺/🇺🇦EUR: 51,45 / 51,65 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

7 Aug 2026, 07:48 UTC660 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,63 / 44,73 🇪🇺/🇺🇦EUR: 51,45 / 51,65 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

7 Aug 2026, 06:08 UTC679 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,61 / 44,71 🇪🇺/🇺🇦EUR: 51,45 / 51,65 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

6 Aug 2026, 13:11 UTC747 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,61 / 44,71 🇪🇺/🇺🇦EUR: 51,45 / 51,65 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

6 Aug 2026, 10:51 UTC762 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,62 / 44,72 🇪🇺/🇺🇦EUR: 51,45 / 51,65 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

6 Aug 2026, 08:58 UTC769 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,65 / 44,75 🇪🇺/🇺🇦EUR: 51,50 / 51,68 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

6 Aug 2026, 08:13 UTC775 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,65 / 44,73 🇪🇺/🇺🇦EUR: 51,50 / 51,67 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

6 Aug 2026, 07:11 UTC764 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,66 / 44,74 🇪🇺/🇺🇦EUR: 51,50 / 51,67 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

6 Aug 2026, 06:16 UTC755 viewsread 8 August 2026

🇺🇸/🇺🇦USD: 44,65 / 44,73 🇪🇺/🇺🇦EUR: 51,48 / 51,64 Приём заявок: - Львовская площадь - @Kasa_kyiv - ст. м. Печерская - @Gkirf888 - ст. м. Лыбедская - @kasa_antonovicha

Showing the 12 most recent of 30 posts we hold for @fortex_exchange_kiev. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 11 October 2026 — this entry's latest reading, not the date you are reading this.

“EXCHANGE KIEV” (@fortex_exchange_kiev), 3,686 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/fortex_exchange_kiev.

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.