Telegram RegisterThe public register of Telegram
Telegram profile photo for CT Live Feed (Automated)

Channel

CT Live Feed (Automated)

@CTLIVEFEED

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

816subscribers

-6 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-1001563460237
TypeChannel
Username@CTLIVEFEED
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live2 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/CTLIVEFEED

Growth

8168228197 August 2026 — 822 subscribers8 August 2026 — 822 subscribers16 August 2026 — 819 subscribers25 August 2026 — 818 subscribers2 September 2026 — 816 subscribers7 August 20262 September 2026
5 measurements spanning 25 days, net -6. 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 815–823 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 00:13816-2
25 Aug 2026, 01:33818-1
16 Aug 2026, 19:14819-3
8 Aug 2026, 01:31822no change
7 Aug 2026, 12:14822first reading

Engagement

20 posts held, back to 6 August 2026the 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 14:47 UTC34 viewsread 8 August 2026

lookonchain: BlackRock has seen 4 consecutive trading days of $BTC net inflows, totaling 9,269 $BTC ($604M).

7 Aug 2026, 13:48 UTC39 viewsread 8 August 2026

lookonchain: August 7 Update: #Bitcoin ETFs: 1D NetFlow: +1,673 $BTC(+$109.16M)🟢 7D NetFlow: +7,306 $BTC(+$476.7M)🟢 #Ethereum ETFs: 1D NetFlow: +42,756 $ETH(+$82.52M)🟢 7D NetFlow: +85,091 $ETH(+$164.22M)🟢 QT: Lookonchain (@lookonchain) August 6 Update: #Bitcoin ETFs: 1D NetFlow: +3,781 $BTC(+$243.49M)🟢 7D NetFlow: +9,034 $BTC(+$581.79M)🟢 #Ethereum ETFs: 1D NetFlow: +27,749 $ETH(+$52.91M)🟢 7D NetFlow: +40

7 Aug 2026, 13:29 UTC40 viewsread 8 August 2026

lookonchain: The 1600BTC-short trader closed another 500 $BTC ($32.58M) to avoid liquidation. The total loss has now exceeded $1.5M. Current position: 900 $BTC($58.6M) New liquidation price: $64,998.73

7 Aug 2026, 13:21 UTC42 viewsread 8 August 2026

lookonchain: After a month of inactivity, Royal Government of Bhutan sold another 434.87 $BTC ($27.93M). arkm.com/explorer/addre…

7 Aug 2026, 07:59 UTC57 viewsread 8 August 2026

lookonchain: Whales continue to accumulate $BTC. Another newly created wallet withdrew 434.87 $BTC($27.96M) from #Binance. arkm.com/explorer/addre…

7 Aug 2026, 05:08 UTC64 viewsread 8 August 2026

lookonchain: The #Coldcard hacker, who stole 2,055 $BTC($130M), is active again. An hour ago, the hacker transferred 30.185 $BTC($1.94M) to a new wallet. arkm.com/explorer/addre…

7 Aug 2026, 03:48 UTC63 viewsread 8 August 2026

lookonchain: Ethereum OG whale 0x7378 keeps buying $LIT. Over the past 2 months, the whale has spent a total of $9.1M to buy 3.91M $LIT at an average price of $2.33. debank.com/profile/0x7378…

7 Aug 2026, 02:24 UTC68 viewsread 8 August 2026

lookonchain: The Jaredfromsubway exploiter is terrible at trading. A month ago, the exploiter stole $7.7M and swapped it for $ETH. The exploiter later sold 2,327 $ETH($3.94M) at $1,695, then bought back 2,063 $ETH($3.94M) at $1,912 10 hours ago. He lost 264 $ETH($505K).…

7 Aug 2026, 01:22 UTC70 viewsread 8 August 2026

lookonchain: Pump fun(@Pumpfun) sold another 84,789 $SOL($6.25M) again today! In total, pump.fun has sold 4,823,325 $SOL($807M) at an average price of $167.4. arkm.com/explorer/entit…

7 Aug 2026, 00:44 UTC66 viewsread 8 August 2026

lookonchain: Bitcoin mining companies are selling $BTC. MARA, which holds 36,303 $BTC($2.34B), deposited 200 $BTC($12.86M) into NYDIG 10 hours ago. Riot Platforms also continues to send $BTC to NYDIG, depositing another 381 $BTC($24.51M) 10 hours ago. arkm.com/explorer/entit……

6 Aug 2026, 16:37 UTC68 viewsread 8 August 2026

cz_binance: 🇹🇭 Thailand confirms 0% capital gains tax on Bitcoin & crypto. 👏

6 Aug 2026, 16:34 UTC67 viewsread 8 August 2026

cz_binance: RT Felix (@felix_fan) Standing in front of the Burj Khalifa again. Goosebumps. Around three years ago I was here talking to a crypto bro based in the UAE. He told me most of his friends use @TrustWallet. I said that was impossible. It lacked this feature, that chain, that polish. He just smiled and…

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

Mentions

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.

Loker Fresh Graduation
@lokerfreshgrad · 29,480
Telegram ranks this channel #8 of 57 here — alongside 56 others — read 8 September 2026
Wu Blockchain News
@wublockchainenglish · 240,886
Telegram ranks this channel #48 of 91 here — alongside 90 others — read 10 August 2026
New Listings Feed
@NewListingsFeed · 57,570
Telegram ranks this channel #53 of 84 here — alongside 83 others — read 23 August 2026
infinityhedge
@infinityhedge · 45,800
Telegram ranks this channel #63 of 87 here — alongside 86 others — read 27 August 2026
Market News Feed
@marketfeed · 38,272
Telegram ranks this channel #68 of 84 here — alongside 83 others — read 31 August 2026
Kirby Crypto
@kirbycrypto · 40,268
Telegram ranks this channel #75 of 83 here — alongside 82 others — read 30 August 2026

This channel appears in 6 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.

“CT Live Feed (Automated)” (@CTLIVEFEED), 816 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/CTLIVEFEED.

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.