❗️Breakout of the Falling Wedge on AGLD/USDT [4H Chart] Possible Target: $0.17775

Channel
Crypto AI by Klondike
@KlondikeAI
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
6,586subscribers
-148 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 | -1001159670702 |
|---|---|
| Type | Channel |
| Username | @KlondikeAI |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/KlondikeAI |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 19 Sept 2026, 02:58 | 6,586 | -20 |
| 14 Sept 2026, 09:39 | 6,606 | -4 |
| 11 Sept 2026, 05:19 | 6,610 | -8 |
| 6 Sept 2026, 04:41 | 6,618 | -14 |
| 2 Sept 2026, 06:44 | 6,632 | -8 |
| 30 Aug 2026, 01:24 | 6,640 | -14 |
| 27 Aug 2026, 08:39 | 6,654 | +5 |
| 24 Aug 2026, 02:07 | 6,649 | -11 |
| 20 Aug 2026, 08:33 | 6,660 | -1 |
| 17 Aug 2026, 13:28 | 6,661 | -35 |
| 13 Aug 2026, 23:55 | 6,696 | -14 |
| 10 Aug 2026, 11:27 | 6,710 | -24 |
| 7 Aug 2026, 18:13 | 6,734 | no change |
| 7 Aug 2026, 10:18 | 6,734 | first reading |
Engagement
94 posts held, back to 5 August 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 11 pages 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 94 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
❕Falling Wedge was formed on LTC/USDT [12H Chart] Possible Target: $49.768
❗️Strong Bullish Convergence was formed on BNB/USDT [4H Chart] Pump is expected.
❗️Strong Bullish Convergence was formed on SEI/USDT [4H Chart] Pump is expected.
❗️Strong Bullish Convergence was formed on ARC/USDT [1H Chart] Pump is expected.
❕Bearish Flag was formed on ENA/USDT [1H Chart] Possible Target: $0.079335
❕Rising Wedge was formed on VIRTUAL/USDT [1H Chart] Possible Target: $0.53681
❕Bullish Pennant was formed on LINK/USDT [1H Chart] Possible Target: $10.0731
❕Bearish Divergence was formed on AAVE/USDT [1H Chart] Be careful with LONG positions.
❗️Strong Bullish Convergence was formed on 1000PEPE/USDT [4H Chart] Pump is expected.
❕Rising Wedge was formed on BANANA/USDT [12H Chart] Possible Target: $2.0881
❗️Strong Bullish Convergence was formed on MEME/USDT [12H Chart] Pump is expected.
Showing the 12 most recent of 94 posts we hold for @KlondikeAI. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
@CryptoKlondike · 59,571
Telegram ranks this channel #18 of 77 here — alongside 76 others — read 22 August 2026
@DiklatDotCo · 52,606
Telegram ranks this channel #33 of 64 here — alongside 63 others — read 27 August 2026
@ggshot · 93,349
Telegram ranks this channel #45 of 87 here — alongside 86 others — read 17 August 2026
@BinanceLiquidations · 180,620
Telegram ranks this channel #45 of 95 here — alongside 94 others — read 12 August 2026
@CryptoScanner100eyes · 31,385
Telegram ranks this channel #46 of 82 here — alongside 81 others — read 6 September 2026
@crypto_futures_king · 39,445
Telegram ranks this channel #50 of 75 here — alongside 74 others — read 30 August 2026
@cryptobullet · 67,275
Telegram ranks this channel #57 of 77 here — alongside 76 others — read 20 August 2026
@CryptoCove · 29,059
Telegram ranks this channel #63 of 75 here — alongside 74 others — read 9 September 2026
@WhaleSniper · 60,264
Telegram ranks this channel #64 of 96 here — alongside 95 others — read 22 August 2026
@crypto_insiders · 198,909
Telegram ranks this channel #64 of 85 here — alongside 84 others — read 13 August 2026
@thebull_crypto · 175,090
Telegram ranks this channel #66 of 88 here — alongside 87 others — read 12 August 2026
@coach · 23,285
Telegram ranks this channel #67 of 75 here — alongside 74 others — read 18 September 2026
@kimoncrypto · 37,722
Telegram ranks this channel #74 of 75 here — alongside 74 others — read 31 August 2026
@Whalesguide · 200,022
Telegram ranks this channel #83 of 91 here — alongside 90 others — read 11 August 2026
This channel appears in 14 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Crypto AI by Klondike” (@KlondikeAI), 6,586 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/KlondikeAI.
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.