Telegram RegisterThe public register of Telegram
Telegram profile photo for Alan Masters

Channel

Alan Masters

@alan_masters

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

31subscribers

+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-1001536355461
TypeChannel
Username@alan_masters
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live24 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/alan_masters

Growth

303130.57 August 2026 — 31 subscribers11 August 2026 — 31 subscribers16 August 2026 — 30 subscribers24 August 2026 — 31 subscribers7 August 202624 August 2026
4 measurements spanning 17 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 30–31 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 14:1631+1
16 Aug 2026, 02:4830-1
11 Aug 2026, 02:4631no change
7 Aug 2026, 04:0431first reading

Engagement

20 posts held, back to 30 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 30 October 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Oct 2025, 09:01 UTC20 viewsread 11 August 2026
Photo

#snx/usdt has shaped the descending channel formation on the weekly timeframe👩‍💻 Great place to accumulate for the next rally📈

30 Oct 2025, 08:46 UTC20 viewsread 11 August 2026
Photo

#wld/usdt has formed the descending channel on the weekly chart🧐 A major bullish wave is expected✈️

30 Oct 2025, 07:34 UTC12 viewsread 11 August 2026

I think the next few months will be final chance for this cycle.

30 Oct 2025, 06:56 UTC6 viewsread 11 August 2026
Photo

Long $JASMY (Max 6x) ↗️ - Entry: 0.009454 - 0.009810 - TP: 0.010573 - 0.011324 - 0.012346 - 0.013332 - SL: 0.009090 👍 There are currently positive on-chain signals at this time Available trading pair on:👉 Binance | MEXC | Bybit | Gate.io | KuCoin | BingX

30 Oct 2025, 06:44 UTC6 viewsread 11 August 2026

💎 Premium Signal 🔴 Short Pair: #FLM/USDT 📊 Entry Price: 1) 0.0263 2) 0.0270 📈 Targets: 1) 0.0261 2) 0.0255 3) 0.0250 4) 0.0244 Stop Loss: 0.0279 Leverage: 10x-20x

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

“Alan Masters” (@alan_masters), 31 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/alan_masters.

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.