Telegram RegisterThe public register of Telegram
Telegram profile photo for TRYREX OFFICIAL CHANNEL

Channel

TRYREX OFFICIAL CHANNEL

@Tryrexofficial

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

3,095subscribers

-59 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002135215907
TypeChannel
Username@Tryrexofficial
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/Tryrexofficial

Growth

3,0953,1543,124.57 August 2026 — 3,154 subscribers7 August 2026 — 3,154 subscribers8 August 2026 — 3,153 subscribers11 August 2026 — 3,151 subscribers14 August 2026 — 3,140 subscribers17 August 2026 — 3,134 subscribers21 August 2026 — 3,124 subscribers24 August 2026 — 3,112 subscribers27 August 2026 — 3,106 subscribers30 August 2026 — 3,095 subscribers7 August 202630 August 2026
10 measurements spanning 23 days, net -59. 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 3,086–3,163 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 01:373,095-11
27 Aug 2026, 03:253,106-6
24 Aug 2026, 12:143,112-12
21 Aug 2026, 03:133,124-10
17 Aug 2026, 18:573,134-6
14 Aug 2026, 19:473,140-11
11 Aug 2026, 00:113,151-2
8 Aug 2026, 09:513,153-1
7 Aug 2026, 13:473,154no change
7 Aug 2026, 13:343,154first reading

Engagement

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

Reaction mix

164 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 33.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5533.5%
👍4929.9%
🔥2314.0%
👎1811.0%
😁74.27%
👏63.66%
🤔31.83%
🤣21.22%
🙊10.61%

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 164reactions 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 14 July 2026 to 31 July 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

31 Jul 2026, 10:29 UTC561 views7 reactionsread 7 August 2026
Photo

$BTC Not much change in the last few days. This structure is weak and about to break down. We can expect Bitcoin to crash to 60,000$ once the move is complete. As I said in my previous post, a move to 64,000$ was possible to eliminate early shorts, and it happened. Now the market looks uncertain. But bears will certainly take over soon and confirm the breakdown.

7

28 Jul 2026, 09:01 UTC872 views13 reactionsread 7 August 2026
Photo

$BTC WARNING ⚠️ Good morning everyone Today Bitcoin broke this expanding wedge to the downside, as bulls were unable to push higher. This means we'll most likely keep crashing until at least 60,000$ as the whole structure broke down. A quick move to 64k to liquidate early shorts is still possible, but in the end I believe we'll crash back down.

👍9🤔31

27 Jul 2026, 15:49 UTC839 views11 reactionsread 7 August 2026
Photo

$BTC Bounced as I expected to 65 700$ Now this looks like a lower high and we're probably going to break this expanding wedge to the downside. if Bitcoin doesn't recover soon, this increases the chances of a continuation down.

👍83

25 Jul 2026, 20:44 UTC887 views10 reactionsread 7 August 2026
Photo

$BTC Everything went exactly as planned We crashed back to 64 000$ Now expecting at least a small bounce from this level. If the bounce is too weak, this means bears have won. Let's see.

5👍5

24 Jul 2026, 11:34 UTC897 views7 reactionsread 7 August 2026
Photo

$BTC As I expected, we got rejected at the highs. 64,000$ incoming.

🔥7

23 Jul 2026, 09:17 UTC857 views7 reactionsread 7 August 2026
Photo

$BTC Good morning This is an expanding wedge ✅

6👍1

22 Jul 2026, 07:55 UTC851 views3 reactionsread 7 August 2026
Photo

$BTC We're starting to get rejected from this resistance. We made a higher high. This rising wedge is still in play. 63-64k is the next target. What's important in these kinds of situations is to watch closely how price reacts at each retest. Slow reaction = breakout in most cases.

👍21

21 Jul 2026, 09:40 UTC838 views5 reactionsread 7 August 2026

A bit of a delayed reaction. But it was a pretty weird WC final match. Argentina only wakes up once the other team scored first, it seems.

👍2🤣21

21 Jul 2026, 09:39 UTC868 views9 reactionsread 7 August 2026
Photo

$BTC Good morning! We made a higher high. Still in this expanding wedge. The most likely outcome is a rejection to 63-64k. Bulls would really surprise me if we kept pumping

👍5👎4

20 Jul 2026, 15:04 UTC793 views10 reactionsread 7 August 2026
Photo

$BTC High volatility. But overall, it looks like we're not making a higher high so far. If we get rejected to 63,000$, this is going to look bearish.

4👍4👎1🙊1

19 Jul 2026, 15:10 UTC763 views8 reactionsread 7 August 2026

Am I dreaming or did England win 6-4 against France? 😁 Hopefully today adults are playing football

😁7🔥1

19 Jul 2026, 15:07 UTC756 views18 reactionsread 7 August 2026

VAMOS ARGENTINA TODAY 🇦🇷🇦🇷🇦🇷

8👎7🔥3

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

“TRYREX OFFICIAL CHANNEL” (@Tryrexofficial), 3,095 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/Tryrexofficial.

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.