Telegram RegisterThe public register of Telegram
Telegram profile photo for ichimoku AZ

Channel

ichimoku AZ

@ichimokuaz

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

101subscribers

-1 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-1001285054955
TypeChannel
Username@ichimokuaz
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live12 September 2026
Measurements held3
Confirmed unchanged5 times, most recently 12 September 2026
On Telegramt.me/ichimokuaz

Growth

101102101.57 August 2026 — 102 subscribers9 August 2026 — 102 subscribers16 August 2026 — 101 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, net -1. 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 101–102 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 03:58101-1
9 Aug 2026, 10:02102no change
7 Aug 2026, 00:19102first reading

Engagement

20 posts held, back to 22 December 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 8 November 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Nov 2022, 16:06 UTC806 viewsread 9 August 2026

There's a lot of bad news, but I think the market will recover https://www.tradingview.com/x/wBWGmX9U/

8 Apr 2022, 18:29 UTC≈1,010 viewsread 9 August 2026

#ANC Entry price near 2.81 Stop loss 5% Take Profit 10% 15% 20% Risk Reward 1:4 https://www.tradingview.com/chart/ANCUSDTPERP/hXZ3JoGs-Long-ANC-RR-1-4/

7 Apr 2022, 04:06 UTC811 viewsread 9 August 2026

#DOGE https://www.tradingview.com/chart/DOGEUSDTPERP/WOLWin1Z-Long-DOGE-TP-15-RR-1-3/ Entry price near 0.141 Stop loss 5% Take Profit 5% 10% 15% Risk Reward 1:3 ——— Update ✅ 8% https://www.tradingview.com/x/DSZIu3I5/ 15%

1 Apr 2022, 13:15 UTC626 viewsread 9 August 2026

#MKRUSDTP Entry price near 2060 Stop loss 6% Take Profit 10% 15% 20% 25% Risk Reward 1:5 https://www.tradingview.com/chart/MKRUSDTPERP/NOyoRTby-MKRUSDT-TP-25/ —— Update ✅ 10% ✅ 15% ✅ 20% https://www.tradingview.com/x/hNvXGAV3/ ❌ 25%

4 Mar 2022, 04:30 UTC591 viewsread 9 August 2026

#SFP Entry price near 0.071 Stop loss 5% Take Profit 15-20% Risk Reward 1:4 https://www.tradingview.com/chart/SFPUSDTPERP/0YLfUTnU-Long-SFP-Take-Profit-15-20/

2 Mar 2022, 10:52 UTC474 viewsread 9 August 2026

#TRB ❌ Hit stop loss https://www.tradingview.com/chart/TRBUSDT/rcTqfSaO-TRBUSDT-TP-20-RR-1-4/

28 Feb 2022, 10:03 UTC421 viewsread 9 August 2026

❌ Hit stop loss Short #TRXUSDT Entry price near 0.0591 Stop loss 5% Take Profit 0.055 0.053 0.050 Risk Reward 1:3 https://www.tradingview.com/chart/TRXUSDT/Tql2qC0U-Short-TRXUSDT-TP-10-15/

18 Feb 2022, 13:07 UTC432 viewsread 9 August 2026

#QTUM Entry price near 7.1 Stop loss 5% Take Profit 7.8 8.2 8.6 Risk Reward 1:4 https://www.tradingview.com/chart/QTUMUSDTPERP/GRO244Hw-QTUM-Target-8-2-8-6/

17 Feb 2022, 16:12 UTC341 viewsread 9 August 2026

#KLAY https://www.tradingview.com/x/P9p0a291/ Entry price near 1.2480 Stop loss 3% Take Profit 12% Risk Reward 1:4

14 Feb 2022, 13:02 UTC335 viewsread 9 August 2026

#GALAUSDT https://www.tradingview.com/chart/GALAUSDT/Avva10hR-GALAUSDT-TP-0-37-0-42/ Entry price near 0.284 Stop loss 6% Take Profit 0.31 0.37 0.42 Risk Reward 1:8

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“ichimoku AZ” (@ichimokuaz), 101 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/ichimokuaz.

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.