Telegram RegisterThe public register of Telegram
Telegram profile photo for Coinbaks

Channel

Coinbaks

@coinbaks

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Advertising · Posts · Posts edited after publishing · Citations · Cite this entry

15,405subscribers

-1,057 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001571676421
TypeChannel
Username@coinbaks
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/coinbaks

Topic

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@coinbaks/6269 · this entry4 Aug 2026, 16:32 UTC@RusCoinMem/10704 Aug 2026, 16:49 UTC0.9917 minutes
@coinbaks/6301 · this entry13 Aug 2026, 20:28 UTC@RusCoinMem/107213 Aug 2026, 20:45 UTC0.9917 minutes
@coinbaks/6357 · this entry31 Aug 2026, 16:41 UTC@RusCoinMem/108231 Aug 2026, 18:21 UTC0.991.6 hours
@coinbaks/6317 · this entry18 Aug 2026, 18:48 UTC@RusCoinMem/107318 Aug 2026, 19:15 UTC0.9927 minutes
@coinbaks/6549 · this entry13 Nov 2026, 18:02 UTC@RusCoinMem/112113 Nov 2026, 18:10 UTC0.987 minutes
@coinbaks/6462 · this entry31 Oct 2026, 12:02 UTC@RusCoinMem/11061 Nov 2026, 09:18 UTC0.9821 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@RusCoinMem9 (8/8 hand-verifiable sample passed)0.9927 minutesthis entry (9–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 213 comparable posts for this entry, running 1 August 2026 to 17 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_source, last confirmed 18 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

15,40516,46215,933.57 August 202617 November 2026
66 measurements spanning 102 days, net -1,057. 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 15,246–16,621 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
17 Nov 2026, 22:5715,405-26
14 Nov 2026, 20:4615,431-30
11 Nov 2026, 21:1615,461-28
10 Nov 2026, 01:2015,489-37
8 Nov 2026, 15:5615,526-12
7 Nov 2026, 10:2615,538-8
6 Nov 2026, 12:5615,546-10
5 Nov 2026, 12:4615,556-10
4 Nov 2026, 13:1515,566-18
3 Nov 2026, 09:5615,584-18
2 Nov 2026, 07:5115,602-10
1 Nov 2026, 06:5915,612-2
31 Oct 2026, 09:0515,614-17
30 Oct 2026, 05:4915,631-11
29 Oct 2026, 06:2615,642-7
28 Oct 2026, 01:3115,649-13
26 Oct 2026, 21:5115,662-11
26 Oct 2026, 01:0815,673-10
25 Oct 2026, 02:2815,683-7
24 Oct 2026, 00:4615,690first reading

Engagement

216 posts held, back to 1 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 82 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.7%
avg views ÷ 15,405 subscribers
Avg views / post
1,640
111 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
111
of 216 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held216 (1 August 2026 – 17 November 2026)
Views total182,192
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 19:28 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.

What this channel posts

Video runtime
1m 05s
Average length
22s

Measured directly from 3 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.

Advertising

Ad load
0.926%
2 of 216 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
1,760
over 2 measured posts
Median views · rest
1,690
over 214 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 216 most recent posts we hold, published 1 August 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 19 of 111 posts held from the last 30 days (17.1%) 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).

17 Nov 2026, 14:17 UTC842 viewsread 17 November 2026

💎 Telegram ужесточает правила! Компания разослала разработчикам уведомления о проверках платежей во всех ботах и мини-приложениях. Новые требования: ➟ GRAM – единственная разрешенная криптовалюта для операций, кроме хранения, обмена и свопов. ➟ Telegram Stars – обязательны для оплаты цифровых товаров и услуг, включая VPN, подписки и доступ к AI-моделям. ➟ Банковские карты – прямая оплата цифровых услуг через сто…

17 Nov 2026, 10:29 UTC≈1,250 viewsread 17 November 2026
Photo

🇹🇷 В Турции мужчину задержали из-за P2P-сделки на $100, совершенной почти два года назад. В аэропорту на паспортном контроле его остановила полиция. Выяснилось, что против него возбуждено уголовное дело об интернет-мошенничестве. Что произошло: ➤ В январе 2025 года он обменял $100 на турецкие лиры через Binance P2P. Позже выяснилось, что часть средств была связана с мошенниками. ➤ Пострадавший обратился в полицию…

17 Nov 2026, 09:10 UTC≈1,270 viewsread 17 November 2026
Photo

😐 Nvidia рискует потерять ключевых сотрудников из-за отставки Дженсена Хуанга (WSJ) Один из руководителей Nvidia направил совету директоров письмо с требованием вернуть Хуанга на пост CEO. В письме говорится, что Хуанг незаменим для компании, а ведущие специалисты уже задумываются об увольнении. Тем временем петиция за возвращение Хуанга собрала более 188,000 подписей. Однако совет директоров пока не рассматривае…

17 Nov 2026, 07:22 UTC≈1,320 viewsread 17 November 2026

❌ Хакеры атаковали 178 популярных сайтов ради кражи криптовалюты. Под удар попали сайты крупных компаний, включая Zoom, CNN, IKEA, HSBC, Salesforce и Equifax. Злоумышленники внедрили вредоносный код через платформу Optimizely, которую компании используют для оптимизации своих сайтов. Что пытались делать хакеры: ➤ Подменять адреса криптокошельков при переводах, перенаправляя средства себе. ➤ Перехватывать данные …

17 Nov 2026, 06:01 UTC≈1,310 viewsread 17 November 2026
Photo

📊 Утренний обзор рынка! Индекс настроения: 13, крайний страх; Доминация Биткоина: 59,3%; Капитализация рынка: $2,2 трлн. @COINBAKS

16 Nov 2026, 20:49 UTC≈1,480 viewsread 17 November 2026

🤝 NVIDIA, IBM и Fermilab объединяются для разработки квантовых технологий. ➟ Компании создают платформу, которая объединит квантовые процессоры IBM с суперкомпьютерами NVIDIA. ➟ Главная цель– ускорить разработку мощных квантовых компьютеров, решить проблему квантовых ошибок и научиться объединять несколько квантовых процессоров. ➟ NVIDIA также представила алгоритм, ускоряющий исследования методов исправления квант…

16 Nov 2026, 20:03 UTC≈1,440 viewsread 17 November 2026
Photo

🐳 Cypherpunk возобновила покупки ZEC! Компания Cypherpunk вернулась к покупкам ZEC на открытом рынке, сообщил CEO. С конца сентября компания купила еще 3775 ZEC на $3,5 млн по средней цене $920. Общие запасы достигли 341,858 ZEC ($303 млн) – это более 2% всех монет в обращении; цель фонда – не менее 5%. Дополнительно Cypherpunk наращивает запасы за счет майнинга. @COINBAKS

16 Nov 2026, 18:00 UTC≈1,410 viewsread 17 November 2026

🧐 Совет Nvidia не планирует возвращать Хуанга! Совет директоров Nvidia заявил, что не рассматривает возможность возвращения Дженсена Хуанга на должность генерального директора. @COINBAKS

16 Nov 2026, 13:52 UTC≈1,510 viewsread 17 November 2026

😳 Abraxas массово распродает HYPE после взлома! Abraxas Capital распродает HYPE и сокращает позиции, чтобы покрыть убытки после инцидента с Lighter. Маркeтмейкер одновременно массово продает HYPE, закрывает SHORT-позиции по HYPE, ZEC и другим активам на Hyperliquid и выводит средства. HYPE уходит партиями по 2500 токенов – около $163 000 за сделку. За последние 24 часа стоимость активов на счете упала до $30,5 мл…

16 Nov 2026, 13:05 UTC≈1,480 viewsread 17 November 2026

🐳 Майкл Сэйлор докупил 485 BTC – $31 млн. Теперь на балансе Strategy 850 849 BTC – $54,5 млрд. @COINBAKS

16 Nov 2026, 11:44 UTC≈1,530 viewsread 17 November 2026

😳 Взлом Lighter на $15,5 млн! Хакер получил доступ к API-ключам маркетмейкера Abraxas Capital и использовал их для вывода средств с Lighter. После получения доступа злоумышленник закрыл позиции пострадавших аккаунтов и создал публичный пул с нулевой комиссией. Он внес $10 000 и получил 99,99% долей пула. USDC пострадавших переводились в пул партиями примерно по $1 млн, после чего средства выводились. Похищенные …

16 Nov 2026, 10:55 UTC≈1,460 viewsread 17 November 2026

😳 Вспышка подозрительных транзакций у DEX Lighter! Пользователи X заметили подозрительные транзакции с кошелька, который связывают с биржей Lighter. С этого адреса могли вывести около $10 млн в USDC – средства частично обменяли на ETH и начали распределять по другим адресам. Информация о взломе пока не подтверждена, команда Lighter ситуацию не комментировала. @COINBAKS

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

Posts edited after publishing

@coinbaks edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
16 November 2026
Most recent edit
16 November 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 4 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“Coinbaks” (@coinbaks), 15,405 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/coinbaks.

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.