#XAU
custom 54112331917657590098custom 52020647239226705463

Channel
@cryptetra
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
39subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002760976668 |
|---|---|
| Type | Channel |
| Username | @cryptetra |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 4 times, most recently 11 October 2026 |
| On Telegram | t.me/cryptetra |
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 30 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 15:15 | 39 | -3 |
| 14 Aug 2026, 14:47 | 42 | +2 |
| 10 Aug 2026, 19:16 | 40 | no change |
| 7 Aug 2026, 17:55 | 40 | first reading |
18 posts held, back to 19 April 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 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 18 posts for this entry, the most recent from 25 June 2026. An engagement rate over an empty window would be a number about nothing.
99 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 31.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5195033767969839232 | 31 | 31.3% | |
| custom 5379773896352355687 | 20 | 20.2% | |
| custom 5202064723922670546 | 17 | 17.2% | |
| custom 5411233191765759009 | 15 | 15.2% | |
| custom 5438496463044752972 | 14 | 14.1% | |
| custom 5409181477298512340 | 1 | 1.01% | |
| custom 5411089297476441876 | 1 | 1.01% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 18 of the 18 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 99 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 19 April 2026 to 25 June 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.
#XAU
custom 54112331917657590098custom 52020647239226705463
#GER40
custom 51950337679698392327
#XAU
custom 51950337679698392325
#EUR
custom 51950337679698392325
#TON
custom 51950337679698392325
#BTC 🪙
custom 53797738963523556875custom 54112331917657590092
#XAU ❤️🔥
custom 51950337679698392326
https://www.tradingview.com/x/8ZV8EhQa/ #BTC 🪙
custom 53797738963523556874
https://www.tradingview.com/x/x3KA4Unp/ #NASDAQ
custom 54384964630447529724
https://www.tradingview.com/x/TK7CtnMQ/ #BTC 🪙
custom 54384964630447529724custom 53797738963523556872
https://www.tradingview.com/x/GBHQo48q/ #XAU 🧱
custom 52020647239226705464
https://www.tradingview.com/x/E9gfjpGh/ #WLD
custom 52020647239226705467
Showing the 12 most recent of 18 posts we hold for @cryptetra. 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Cryptetra” (@cryptetra), 39 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/cryptetra.
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.