Telegram RegisterThe public register of Telegram
Telegram profile photo for Elliot waves analyst📈📉

Channel

Elliot waves analyst📈📉

@waveanalyst

On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry

8,132subscribers

+205 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001392200837
TypeChannel
Username@waveanalyst
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/waveanalyst

Growth

7,9238,1328,027.57 August 2026 — 7,927 subscribers7 August 2026 — 7,927 subscribers7 August 2026 — 7,926 subscribers10 August 2026 — 7,923 subscribers13 August 2026 — 7,931 subscribers16 August 2026 — 7,938 subscribers19 August 2026 — 7,953 subscribers23 August 2026 — 7,973 subscribers26 August 2026 — 8,028 subscribers30 August 2026 — 8,100 subscribers2 September 2026 — 8,132 subscribers7 August 20262 September 2026
11 measurements spanning 26 days, net +205. 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 7,892–8,163 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 07:048,132+32
30 Aug 2026, 04:048,100+72
26 Aug 2026, 17:438,028+55
23 Aug 2026, 21:177,973+20
19 Aug 2026, 23:227,953+15
16 Aug 2026, 16:227,938+7
13 Aug 2026, 10:077,931+8
10 Aug 2026, 06:167,923-3
7 Aug 2026, 13:297,926-1
7 Aug 2026, 04:457,927no change
7 Aug 2026, 04:377,927first reading

Engagement

65 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.5%
avg views ÷ 8,132 subscribers
Avg views / post
1,260
50 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
50
of 65 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 August 2026
Posts held65 (27 July 202625 August 2026)
Views total62,859
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 19:17 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

25 Aug 2026, 05:38 UTC≈1,290 viewsread 28 August 2026
Photo

DXY dollar index .. 1h . Once we start trading wave (5) then we will be buying EURUSD ,GBPUSD ,AUDUSD . And selling USDJPY USDCAD AND USDCHD

24 Aug 2026, 08:09 UTC≈1,650 viewsread 28 August 2026
Photo

XAUUSD (GOLD) 4H .. we are now starting the correction phase wave (4) ..

24 Aug 2026, 08:07 UTC≈1,380 viewsread 28 August 2026
Photo

XAGUSD ( silver ) I think we have completed all five sub-waves of this wave (3) now we are entering the correction phase of wave (4)

24 Aug 2026, 08:04 UTC≈1,180 viewsread 28 August 2026
Photo

USDCAD 4H ,, this week this pair should continue with the bearish drop targeting 1.300

24 Aug 2026, 08:02 UTC898 viewsread 28 August 2026
Photo

GBPUSD .. following EURUSD with the bullish push . All of these will be bullish because the dollar index should show weakness this week as part of its season behaviour

24 Aug 2026, 08:00 UTC935 viewsread 28 August 2026
Photo

We should continue with this bullish push this week as we are trying to trade the final wave 5 of this (c) wave

20 Aug 2026, 06:53 UTC≈1,900 viewsread 28 August 2026

These past two month the market has been truly quite yesterday we had a huge price movement but it came late during Newyork . Lets see if price will keep moving in this energetic manner

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Elliott Wave Strategy
@ewstrategy · 61,079
Telegram ranks this channel #3 of 89 here — alongside 88 others — read 22 August 2026
Elliott Wave Count
@elliottwavecount · 195,590
Telegram ranks this channel #3 of 88 here — alongside 87 others — read 11 August 2026
Forex.Doc by San Shone
@forexdochtc2 · 34,895
Telegram ranks this channel #52 of 92 here — alongside 91 others — read 2 September 2026
Tania Trading Academy 👑
@TaniaTradingAcademy · 45,753
Telegram ranks this channel #68 of 73 here — alongside 72 others — read 27 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Elliot waves analyst📈📉” (@waveanalyst), 8,132 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/waveanalyst.

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.