Telegram RegisterThe public register of Telegram
Telegram profile photo for TradeLogs - Global 🌐

Channel

TradeLogs - Global 🌐

@TradeLogsGlobal

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

2,961subscribers

-13 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001337575016
TypeChannel
Username@TradeLogsGlobal
Created12 March 2019 β€” measured β€” cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live5 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/TradeLogsGlobal

Growth

2,9612,9742,967.56 August 2026 β€” 2,974 subscribers6 August 2026 β€” 2,974 subscribers10 August 2026 β€” 2,969 subscribers13 August 2026 β€” 2,968 subscribers16 August 2026 β€” 2,969 subscribers20 August 2026 β€” 2,972 subscribers24 August 2026 β€” 2,971 subscribers26 August 2026 β€” 2,968 subscribers29 August 2026 β€” 2,964 subscribers5 September 2026 β€” 2,961 subscribers6 August 20265 September 2026
10 measurements spanning 30 days, net -13. 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 2,959–2,976 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 03:152,961-3
29 Aug 2026, 13:342,964-4
26 Aug 2026, 15:242,968-3
24 Aug 2026, 01:562,971-1
20 Aug 2026, 02:332,972+3
16 Aug 2026, 21:032,969+1
13 Aug 2026, 11:462,968-1
10 Aug 2026, 09:272,969-5
6 Aug 2026, 23:302,974no change
6 Aug 2026, 06:482,974first reading

Engagement

20 posts held, back to 6 May 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 3 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 20 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

254 reactions across 20 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
πŸ‘254100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities β€” πŸ™ is thanks in one channel and mourning in another β€” so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one β€” 4.34K, 1.2M β€” so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post β€” not by adding up the per-emoji breakdown above β€” those same posts carry 254 reactions in total: the kind of figure the paragraph above means by β€œa reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 May 2026 to 1 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

1 Aug 2026, 10:57 UTC558 views12 reactionsread 8 August 2026

πŸ“œSadly, we didn't get the move we were hoping for. We've closed our spot BTC position here at $63K. It will probably take another 2–3 months for the market to bottom out.

πŸ‘12

27 Jul 2026, 15:27 UTCβ‰ˆ1,070 views15 reactionsread 8 August 2026
Photo

πŸ“Š $BTC 1W: If BTC is unable to move above 66k by the end of this month then we will close our spot buy position. The market could turn nasty if the price gets rejected here.

πŸ‘15

14 Jul 2026, 16:54 UTCβ‰ˆ1,290 views6 reactionsread 8 August 2026

πŸ“œπŸ‘† No new update, unless we go below 61k this idea should work.

πŸ‘6

10 Jul 2026, 09:30 UTCβ‰ˆ1,530 views8 reactionsread 8 August 2026

πŸ“œπŸ‘†πŸ»If the price goes to 61k, this trade idea will be invalid, so you can use a stop loss there in case you are following this idea.

πŸ‘8

7 Jul 2026, 07:02 UTCβ‰ˆ1,830 views13 reactionsread 8 August 2026
Photo

πŸ“Š$BTC 1W: If BTC makes this move, it could start a rally, but we are not very confident about it, so just trading the spot market only. Don't think BTC will bottom out before October or November, and the final 2-3 months of a bear markets are usually a bit violent, so we are being cautious.

πŸ‘13

5 Jul 2026, 22:59 UTCβ‰ˆ1,580 views10 reactionsread 8 August 2026
Photo

πŸ“Š $BTC 1D: Open interest reset was not done fully but this is pretty strong bullish divergence. Weekly chart is also printing bullish divergence. Bought a small amount of Spot BTC here, we will update if this idea invalidates. 66k-67k is important level if it can break that level then it should test 83k areas.

πŸ‘10

25 Jun 2026, 05:56 UTCβ‰ˆ1,690 views15 reactionsread 8 August 2026
Photo

πŸ“Š BTCUSD 1D: Waiting for open interest to be fully wiped out before looking for long entries. Although we believe it will take another 2–3 months for BTC to bottom out, we will look for 10–15% moves to trade until then. These will be short-term positions only, not long-term. Keep patience.

πŸ‘15

18 Jun 2026, 16:19 UTCβ‰ˆ1,700 views12 reactionsread 8 August 2026

πŸ“œClosed the spot BTC position from 66k at 3.6% loss.

πŸ‘12

15 Jun 2026, 15:24 UTCβ‰ˆ1,900 views14 reactionsread 8 August 2026
Photo

πŸ“Š BTC 2H (CME): 78500 CME gap, weakly close was good BTC could chase that level. We have a spot BTC buy position from 66k. Still it is below previous important support so be cautious with leveraged positions.

πŸ‘14

12 Jun 2026, 06:40 UTCβ‰ˆ1,670 views15 reactionsread 8 August 2026
Photo

πŸ“Š $BTC 4H: Consolidating below support is not a very good thing. Still staying sidelined. We don't expect much of a bullish move before September-October, so the next few months are going to be dull like this, IMO.

πŸ‘15

8 Jun 2026, 06:46 UTCβ‰ˆ1,800 views19 reactionsread 8 August 2026

πŸ“œπŸ‘†πŸ»Market Update: Bitcoin will probably bottom out in next 5–6 months. Markets are usually very volatile and choppy during a bottoming phase, so be patient and trade cautiously. If we start seeing bad news and FUD, that could be a sign that we're getting close to the bottom. It's been a long time since this market experienced any significant negative news, so let's see what the next 5–6 months bring. Our main goal sh…

πŸ‘19

6 Jun 2026, 06:13 UTCβ‰ˆ1,620 views18 reactionsread 8 August 2026
Photo

πŸ“Š $BTC 1D: That open interest needs to be completely wiped out before we think about taking new long entries. Around $1 billion in positions still needs to be closed or liquidated. We'll wait until then.

πŸ‘18

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

100eyes Crypto Scanner (PREVIEW)
@CryptoScanner100eyes Β· 31,538
Telegram ranks this channel #57 of 82 here β€” alongside 81 others β€” read 6 September 2026
Kim & Crypto
@kimoncrypto Β· 37,952
Telegram ranks this channel #60 of 75 here β€” alongside 74 others β€” read 31 August 2026
Trade & Grow (Crypto) HWP
@Crypto_HOLDwithPriyank Β· 28,527
Telegram ranks this channel #67 of 84 here β€” alongside 83 others β€” read 9 September 2026
Klondike (Crypto Rush) ⚠️
@CryptoKlondike Β· 59,838
Telegram ranks this channel #71 of 77 here β€” alongside 76 others β€” read 22 August 2026
JustTopIco
@JustTopico Β· 34,157
Telegram ranks this channel #83 of 85 here β€” alongside 84 others β€” read 3 September 2026
D Man
@blockchainwhispersbaby Β· 100,171
Telegram ranks this channel #84 of 91 here β€” alongside 90 others β€” read 15 August 2026
CryptoQuant
@cryptoquant_official Β· 55,890
Telegram ranks this channel #87 of 94 here β€” alongside 93 others β€” read 23 August 2026

This channel appears in 7 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 5 September 2026 β€” this entry's latest reading, not the date you are reading this.

β€œTradeLogs - Global πŸŒβ€ (@TradeLogsGlobal), 2,961 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/TradeLogsGlobal.

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.