https://www.youtube.com/live/1o39Ms1g5V4?si=F8biAA6CvsoDyaP7

Channel
Ak forex trader
@akforex2000
On this record: Topic · Growth · Engagement · Posts · Cite this entry
693subscribers
+60 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002758347444 |
|---|---|
| Type | Channel |
| Username | @akforex2000 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/akforex2000 |
Topic
Crypto & trading — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 14:02 | 693 | -7 |
| 29 Sept 2026, 09:22 | 700 | +25 |
| 15 Sept 2026, 05:20 | 675 | +31 |
| 7 Sept 2026, 12:16 | 644 | +11 |
| 30 Aug 2026, 09:57 | 633 | +2 |
| 24 Aug 2026, 05:48 | 631 | -7 |
| 16 Aug 2026, 13:59 | 638 | +4 |
| 8 Aug 2026, 14:41 | 634 | +1 |
| 8 Aug 2026, 02:50 | 633 | no change |
| 7 Aug 2026, 17:03 | 633 | first reading |
Engagement
20 posts held, back to 8 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 1 page 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 20 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
https://www.youtube.com/live/8IpSAPK6ICo?si=zJEe7esRs0FNmWPb
+90 PIPS TARGET 1 HIT (1:1)✅ SET BREAKEVEN https://www.tradingview.com/x/V5ciqgoq/
SET BREAKEVEN NOW https://www.tradingview.com/x/6P0qbj87/
GOLD BUY NOW SL: 4048.88 https://www.tradingview.com/x/hHSz0obf/
+90 PIPS TARGET 1 HIT✅ https://www.tradingview.com/x/xdVMdrJC/
https://www.youtube.com/live/_8G_jW-yy0Y?si=WPmz7-FD9JpfuHPQ
https://www.youtube.com/live/lz6OzBNZPDc?si=B3dPirO9Miuu3TBt
https://www.youtube.com/live/Xx1a4cgiomM?si=e1jP1Xu5n8ejGrK1
https://www.youtube.com/live/OIPvpybRUxQ?si=j52zeghaVT8eunwO
https://www.youtube.com/live/mwd2nSuwGV8?si=cgIEew_hYFroftLy
https://www.youtube.com/live/65ocfG-09qo?si=ahnm-FGCv1O3SzZD
Showing the 12 most recent of 20 posts we hold for @akforex2000. 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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“Ak forex trader” (@akforex2000), 693 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/akforex2000.
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.