Channel
@Metazen_financial_services
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
10,607subscribers
-4,237 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001599415974 |
|---|---|
| Type | Channel |
| Username | @Metazen_financial_services |
| Created | Between 1 August 2021 and 31 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 57 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/Metazen_financial_services |
Gambling & betting — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 21:44 | 10,607 | -69 |
| 4 Nov 2026, 22:56 | 10,676 | -83 |
| 3 Nov 2026, 22:30 | 10,759 | -19 |
| 3 Nov 2026, 01:09 | 10,778 | -43 |
| 2 Nov 2026, 02:46 | 10,821 | -13 |
| 1 Nov 2026, 05:49 | 10,834 | -28 |
| 31 Oct 2026, 06:45 | 10,862 | -26 |
| 30 Oct 2026, 04:58 | 10,888 | -18 |
| 29 Oct 2026, 08:28 | 10,906 | -24 |
| 28 Oct 2026, 03:17 | 10,930 | -7 |
| 27 Oct 2026, 05:06 | 10,937 | -20 |
| 26 Oct 2026, 03:48 | 10,957 | -34 |
| 25 Oct 2026, 03:20 | 10,991 | -79 |
| 24 Oct 2026, 06:20 | 11,070 | -17 |
| 23 Oct 2026, 04:50 | 11,087 | -106 |
| 22 Oct 2026, 03:51 | 11,193 | -50 |
| 20 Oct 2026, 20:17 | 11,243 | -12 |
| 19 Oct 2026, 17:51 | 11,255 | -17 |
| 18 Oct 2026, 17:16 | 11,272 | -13 |
| 17 Oct 2026, 20:18 | 11,285 | first reading |
34 posts held, back to 20 June 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 58 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 November 2026 |
|---|---|
| Posts held | 34 (20 June 2026 – 2 November 2026) |
| Views total | 673 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 20:27 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
11 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 54.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 54.5% | |
| 👏 | 3 | 27.3% | |
| 🔥 | 1 | 9.09% | |
| 🥰 | 1 | 9.09% |
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 6 of the 34 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 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 34 most recent posts we hold, published 20 June 2026 to 2 November 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.
Telegram’s own ‘edited’ marker: 0 of 13 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
BTC 4 red weekly closes in a row. Last 17 times this happened, the next week closed green 13 times (76%). This week we start -1.9% from the open lol. Let's see.
Signed Metazen Assist [NEVER DM FIRST ]
the $BTC weekly high in? Only 26% of weeks had their high in by Monday night (415 weeks) Even in red weeks, 73% printed the high later. 78.8k probably not the top of the week imo.
Signed Metazen Assist [NEVER DM FIRST ]
BTC Midterm Report | Is This Time Different? Historical pattern: • 2018: –50% after midterms (BCH fork catalyst). Bottom ~39 days later. • 2022: –15 to –25% after midterms (FTX). Bottom ~13 days later. Both driven by crypto-specific shocks, not the elections themselves. Midterms just lined up with late-stage bear markets. This time looks different: • Low already printed July 1 at ~$58k (125 days *before* the elect…
Signed Metazen Assist [NEVER DM FIRST ]
It is hard to ignore the imbalance in liquidations to the downside. Deleverage if you need to
Signed Metazen Assist [NEVER DM FIRST ]
$BTC Interesting. Both spot and futures CVD are grinding higher, yet price is still getting rejected hard from the $79k area. This creates a bullish CVD divergence and is considered an early sign of a potential reversal. Of course, this doesn’t guarantee a move to the upside and we’ll still have to wait for structure to confirm the move, but it’s definitely something worth keeping an eye on.
Signed Metazen Assist [NEVER DM FIRST ]
#BTC Last pump from 79k to 81k stopped because of fucking binance hack after partial booking stopped at entry As of now looking for new opportunities
Signed Metazen Assist [NEVER DM FIRST ]
#BTC Sooo far sooo Good From 79k range to 81k 🤝
Signed Metazen Assist [NEVER DM FIRST ]
$BTC $80K bid liquidity taken & shorts continuing to dominate perp positioning here Short squeeze is loading 💫 Not a financial advice
Signed Metazen Assist [NEVER DM FIRST ]
JUST IN: 🚨🚨 Crypto is dumping $SOL falls under $100 $XRP falls under $1.30 $ETH falls under $2,350 Bitcoin $BTC falls under $80,000 Over $200,000,000 in leveraged crypto long positions have been liquidated in the past 60 minutes.
Signed Metazen Assist [NEVER DM FIRST ]
Photo, posted without a caption
Signed Metazen Assist [NEVER DM FIRST ]
Bitcoin drops to 79K Oil jumps on reports that Zelensky sabotaged ceasefire efforts and attacked Omsk. Oil weekend indications
Signed Metazen Assist [NEVER DM FIRST ]
82k ---85k----89k---- loading
Signed Metazen Assist [NEVER DM FIRST ]
Showing the 12 most recent of 34 posts we hold for @Metazen_financial_services. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“Trading services By Metazen” (@Metazen_financial_services), 10,607 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Metazen_financial_services.
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.