Telegram RegisterThe public register of Telegram
Telegram profile photo for www.luckydragon.ai -Official Channel-

Channel

www.luckydragon.ai -Official Channel-

@LuckyDragonAI

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

34subscribers

+0 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-1001423890523
TypeChannel
Username@LuckyDragonAI
CreatedBetween 1 April 2019 and 5 January 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/LuckyDragonAI

Growth

333433.57 August 2026 — 34 subscribers11 August 2026 — 34 subscribers17 August 2026 — 33 subscribers31 August 2026 — 34 subscribers7 August 202631 August 2026
4 measurements spanning 23 days. 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 33–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 05:4334+1
17 Aug 2026, 09:3833-1
11 Aug 2026, 00:4634no change
7 Aug 2026, 21:5534first reading

Engagement

20 posts held, back to 5 January 2021the 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 26 November 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

26 Nov 2021, 19:50 UTC265 viewsread 11 August 2026

Hey all, we will disable M2 for today due to the spike in volatility.

22 Oct 2021, 18:26 UTC308 viewsread 11 August 2026

Hey all. We will run M2 just during the last 30 minutes of the session. M1 will trade normally.

21 Sept 2021, 18:50 UTC362 viewsread 11 August 2026

Hey everyone. We will run the current week just with M1 due to the increase in market volatility and uncertainty.

28 Jul 2021, 18:56 UTC462 viewsread 11 August 2026

Hey all. We will turn on M2 during the last hour of the trading window today. We are still considering not trading today.

20 Jul 2021, 18:31 UTC508 viewsread 11 August 2026

Hey everbody. We will not trade M2 today because of the spike in volatility.

15 Jul 2021, 18:14 UTC485 viewsread 11 August 2026

Hello everyone. We will continue to run half risk on M2 today due to the volatility spike.

14 Jul 2021, 18:41 UTC430 viewsread 11 August 2026

Hey everybody. We will trade M2 at half risk today due to the volatility earlier in the session.

9 Jul 2021, 17:37 UTC417 viewsread 11 August 2026

Hello everyone. We will not run M2 today due to G20 meetings.

16 Jun 2021, 18:53 UTC427 viewsread 11 August 2026

Hello everyone. We decided to shut M2 off today due to the strong volatility going into the trading window.

28 May 2021, 19:45 UTC476 viewsread 11 August 2026

Hey all. We decided to close the M2 positions and enabled Cycle Down for today's session.

30 Apr 2021, 17:22 UTC525 viewsread 11 August 2026

Strong trend for the GBPCAD at the moment. We are turning off mode 2 for today's session.

Showing the 12 most recent of 20 posts we hold for @LuckyDragonAI. 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 31 August 2026 — this entry's latest reading, not the date you are reading this.

“www.luckydragon.ai -Official Channel-” (@LuckyDragonAI), 34 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/LuckyDragonAI.

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.