Channel
@quoteX
On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Posts · Polls · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,397,286subscribers
-97,709 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001897923732 |
|---|---|
| Type | Channel |
| Usernames | @caixa @paytm @quoteX @utkarsh @winzo |
| Created | Between 1 November 2022 and 31 July 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 179 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/quoteX |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 47% 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 |
|---|---|---|
| 6 Oct 2026, 13:15 | 1,397,286 | -1,098 |
| 6 Oct 2026, 00:16 | 1,398,384 | -110 |
| 5 Oct 2026, 22:18 | 1,398,494 | -1,570 |
| 4 Oct 2026, 23:39 | 1,400,064 | -752 |
| 4 Oct 2026, 12:01 | 1,400,816 | -5,268 |
| 1 Oct 2026, 10:01 | 1,406,084 | -660 |
| 30 Sept 2026, 18:19 | 1,406,744 | -295 |
| 30 Sept 2026, 12:56 | 1,407,039 | -5,061 |
| 27 Sept 2026, 17:17 | 1,412,100 | -2,911 |
| 26 Sept 2026, 00:58 | 1,415,011 | -7,423 |
| 19 Sept 2026, 07:37 | 1,422,434 | -1,512 |
| 18 Sept 2026, 12:18 | 1,423,946 | -671 |
| 18 Sept 2026, 02:58 | 1,424,617 | -61 |
| 18 Sept 2026, 01:19 | 1,424,678 | -248 |
| 17 Sept 2026, 20:15 | 1,424,926 | -1,649 |
| 16 Sept 2026, 19:40 | 1,426,575 | -1,380 |
| 16 Sept 2026, 01:40 | 1,427,955 | -96 |
| 15 Sept 2026, 23:57 | 1,428,051 | -16 |
| 15 Sept 2026, 23:41 | 1,428,067 | -230 |
| 15 Sept 2026, 19:41 | 1,428,297 | first reading |
1,648 posts held, back to 5 August 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 130 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.
| Window | Rolling 30 days · latest post in window 6 October 2026 |
|---|---|
| Posts held | 1,648 (5 August 2026 – 6 October 2026) |
| Views total | 4,829,117 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Oct 2026, 19:31 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 11 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 625 of this channel’s own posts over the last 30 days (18 of the 24-hour readings behind this are interpolated, not measured directly): across 602 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 8.7 hours of being posted; a typical post has already reached 23.6% of its 24-hour view count within the first hour, and 61.8% within the first six; the median 24-hour reach across those posts is 4,620 views — 0.331% of this channel’s own subscriber count (90th percentile 5,489).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /403236 Oct 2026, 15:21 UTC | 824 minutes – 4.2 hours old | 2,140 views ~no reaction reading | 60 minutes: 1,091 interp. → 3.0 hours: 1,900still climbing at last reading | not yet at 24h | 58 minutesprovisional — final view count still climbing |
| /403226 Oct 2026, 15:20 UTC | 825 minutes – 4.2 hours old | 2,050 views ~no reaction reading | 60 minutes: 1,107 interp. → 3.0 hours: 1,850still climbing at last reading | not yet at 24h | 51 minutesprovisional — final view count still climbing |
| /403216 Oct 2026, 15:20 UTC | 825 minutes – 4.2 hours old | 1,960 views ~no reaction reading | 60 minutes: 1,081 interp. → 3.0 hours: 1,780still climbing at last reading | not yet at 24h | 49 minutesprovisional — final view count still climbing |
| /403206 Oct 2026, 15:19 UTC | 826 minutes – 4.2 hours old | 1,950 views ~no reaction reading | 60 minutes: 1,103 interp. → 3.0 hours: 1,780still climbing at last reading | not yet at 24h | 44 minutesprovisional — final view count still climbing |
| /403196 Oct 2026, 15:19 UTC | 826 minutes – 4.2 hours old | 1,960 views ~no reaction reading | 60 minutes: 1,111 interp. → 3.0 hours: 1,780still climbing at last reading | not yet at 24h | 43 minutesprovisional — final view count still climbing |
| /403186 Oct 2026, 15:19 UTC | 826 minutes – 4.2 hours old | 1,960 views ~no reaction reading | 60 minutes: 1,111 interp. → 3.0 hours: 1,790still climbing at last reading | not yet at 24h | 43 minutesprovisional — final view count still climbing |
| /403176 Oct 2026, 15:19 UTC | 827 minutes – 4.2 hours old | 1,980 views ~no reaction reading | 60 minutes: 1,100 → 3.0 hours: 1,770still climbing at last reading | not yet at 24h | 43 minutesprovisional — final view count still climbing |
| /403166 Oct 2026, 15:18 UTC | 827 minutes – 4.2 hours old | 2,020 views ~no reaction reading | 60 minutes: 1,170 → 3.0 hours: 1,840still climbing at last reading | not yet at 24h | 40 minutesprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
1️⃣Friends, I want to let you know that we’ll be posting plenty of trades on the @Quotex channel today—we’re keeping the trading going! Want to keep trading with us? Just drop us a message. VIP channel | AI assistant
1 MORE?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Photo, posted without a caption
DOWN
1 MINUTES
USD/BRL (OTC)
GO
go
Would you like to receive a trading signals today on the @Quotex platform?) in 40 minutes @quotex subscribe so you don’t miss out!
Shares as published. No per-option vote count is published by Telegram, so none is shown.
💸 Bro, you really gonna keep watching me stack profits while you hesitate? The signals are 🔥 and the window’s closing fast. Don’t be that guy crying later – DM me @to_trade and let’s get you earning. ⚡️
📊Join the VIP channel. Make profit together.📊
✅Do you want even more trading deals? I promise to come back here and give you a high-quality deal! Want to get more than just one deal? Just message me, and I’ll add you to my team! Join me! VIP channel | AI assistant
Showing the 12 most recent of 1,648 posts we hold for @quoteX. 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.
The 6 most recent of 157 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
1 MORE?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Would you like to receive a trading signals today on the @Quotex platform?) in 40 minutes @quotex subscribe so you don’t miss out!
Shares as published. No per-option vote count is published by Telegram, so none is shown.
1 more deal?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Would you like to receive a trading signals today on the @Quotex platform?) in 40 minutes @quotex subscribe so you don’t miss out!
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Would you like to receive a trading signals today on the @Quotex platform?) in 40 minutes @quotex subscribe so you don’t miss out!
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Would you like to receive a trading signals today on the @Quotex platform?) in 40 minutes @quotex subscribe so you don’t miss out!
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 30 August 2026 to 6 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Named by 12 registered channels — 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 10 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 199 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
One domain this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“Quotex Trading” (@quoteX), 1,397,286 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/quoteX.
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.