Other / unclassifiable — 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 77% 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.
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 word for word on 2 other registered channels. 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)
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 12 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 434 comparable posts for this entry, running 11 January 2021 to 2 August 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).
Across the whole group of 3, the earliest publisher we hold is @cryptobotru. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, last confirmed 6 August 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
108 measurements spanning 61 days, net -190,128. 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 1,465,412–1,712,578 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 108
Measured (UTC)
Subscribers
Change
5 Oct 2026, 15:57
1,493,931
-471
5 Oct 2026, 11:17
1,494,402
-3,159
4 Oct 2026, 06:57
1,497,561
-11,893
29 Sept 2026, 22:42
1,509,454
-2,386
29 Sept 2026, 08:55
1,511,840
-11,820
25 Sept 2026, 12:02
1,523,660
-15,274
19 Sept 2026, 03:41
1,538,934
-3,632
17 Sept 2026, 23:59
1,542,566
-109
17 Sept 2026, 20:19
1,542,675
-3,472
16 Sept 2026, 15:38
1,546,147
-2,912
15 Sept 2026, 19:17
1,549,059
no change
15 Sept 2026, 18:00
1,549,059
-2,153
14 Sept 2026, 22:40
1,551,212
-2,079
14 Sept 2026, 01:21
1,553,291
no change
13 Sept 2026, 23:41
1,553,291
-2,573
13 Sept 2026, 11:01
1,555,864
-4,676
12 Sept 2026, 08:57
1,560,540
no change
12 Sept 2026, 08:40
1,560,540
-1,428
11 Sept 2026, 15:01
1,561,968
-2,834
10 Sept 2026, 04:15
1,564,802
first reading
Engagement
1,256 posts held, back to 15 August 2019 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 674 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.321%
avg views ÷ 1,493,931 subscribers
Avg views / post
4,800
16 posts measured
Reaction rate
0.965%
reactions ÷ views · ER floor
Posts in window
16
of 1,256 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
Window
Rolling 30 days · latest post in window 6 October 2026
Posts held
1,256 (15 August 2019 – 6 October 2026)
Views total
76,790
Reactions total
741
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Oct 2026, 20:00 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
Photos
425
Videos
67
Links
552
Lifetime counters from Telegram’s own channel header, read 6 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
2m 57s
Average length
25s
Measured directly from 7 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.
View velocity
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 12 of this channel’s own posts over the last 30 days: across 11 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 34 hours of being posted; a typical post has already reached 36.3% of its 24-hour view count within the first hour, and 75.7% within the first six; the median 24-hour reach across those posts is 1,840 views — 0.123% of this channel’s own subscriber count (90th percentile 2,320).
8 most recently posted, with a view-velocity reading
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.
Reaction mix
3,293 reactions across 72 posts, in 5 distinct kinds. The most used accounts for 34.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤣
1,131
34.3%
🔥
820
24.9%
👍
618
18.8%
😁
527
16.0%
🌚
197
5.98%
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 986 of the 1,000 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 233,620 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 31 July 2022 to 6 October 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 Stars
Stars received
530
across the posts below
Posts paid on
10
of 987 we hold a reading for · 1%
Most on one post
508
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tonbase. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 31 July 2022 to 6 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Самоё интересное, что покупкой нового сервера, написанием этого агента, выдачей доступов, развертыванием и проверкой тоже занимался другой агент.
Я просто голосом надиктовал агенту с доступом к инфре свою идею и через пол часа проект начал анализировать и развивать самостоятельный самоулучшающийся агент.
Причем он извиняется и сам исправляется, если понимает, что заспамил меня своими мыслями и делает это чуть реже …
Теперь мною открыт ещё один новый уровень.
На отдельном сервере запущен Claude Code, который имеет доступ к базе, к clickhouse, к коду и сам постоянно изучает проект – поведение пользователей, баги, маркетинг и неизвестные мне возможности этого агента, потому что он сам пишем себя постоянно улучшает.
В результате, со вчерашнего вечера, и, продолжая работать сегодня ночью он нашел три существенных проблемы, которые …
Постепенно у меня стёрлись границы между этапами разработки.
Раньше всё было понятно: написал код, закоммитил, проверил PR. Потом пошёл на сервер, задеплоил руками.
Каждый этап – отдельное действие, на которое нужно переключиться.
Теперь я просто ставлю задачу агенту и уже не всегда знаю, что он делает и где. На локалке, в worktree, в облаке, на сервере, в ядре Linux или уже что-то физически меняет в датацентре (н…
Самое безумное, что мой мозг до сих пор не может вместить то, что ИИ выполняет любую задачу и никогда не пишет «я не могу».
И мозг не понимает, как такое возможно, ведь раньше это было невозможно, а теперь просто нужно подождать несколько минут.
Я только хотел впервые за месяц выйти из дома прогуляться на 2 минуты.
Эх, придется отложить прогулку.
anthropic.com/claude-opus-5-5
😁17🔥9🤣6👍1
Showing the 12 most recent of 1,256 posts we hold for @tonbase. 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
@tonbase edited 2 posts 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
18 August 2026
Most recent edit
3 September 2026
Forward network
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.
Mentions
Named by 40 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Handles this channel named that no longer answer
Dead references
8
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
7
vacant every time we have ever looked
@tonbase named 8 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@tonpayru named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 4 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@thegram named in 16 posts, 8 August 2026 – 8 August 2026
@auction named in 4 posts, 8 August 2026 – 8 August 2026
@tonboss named in 3 posts, 8 August 2026 – 8 August 2026
@flootonch named in 2 posts, 8 August 2026 – 8 August 2026
@ton_traders_ru named in 1 post, 8 August 2026 – 8 August 2026
@tonbasechaten named in 1 post, 8 August 2026 – 8 August 2026
@bullschat named in 1 post, 8 August 2026 – 8 August 2026
Channels Telegram recommends alongside this one
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.
Новости Walt (ранее Кошелёк) @walt_news_cis · 1,110,581#1
Read from Telegram’s recommendation API, most recently 23 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.
Appears in Telegram’s recommendations for other channels
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.
Русский TON @ruton · 126,391 Telegram ranks this channel #3 of 58 here — alongside 57 others — read 30 August 2026
Roxman печатает… @roxtalk · 472,963 Telegram ranks this channel #3 of 90 here — alongside 89 others — read 25 August 2026
Deep Ton @DeepTon · 19,239 Telegram ranks this channel #5 of 84 here — alongside 83 others — read 2 October 2026
🦄 Max.ton @gramlow · 19,652 Telegram ranks this channel #7 of 83 here — alongside 82 others — read 20 September 2026
Дело в TON @delo_vton · 46,533 Telegram ranks this channel #7 of 64 here — alongside 63 others — read 27 August 2026
Vibes @saintvibes · 48,445 Telegram ranks this channel #7 of 75 here — alongside 74 others — read 24 August 2026
JpegMillionaire @jpegmillionaire · 25,365 Telegram ranks this channel #8 of 82 here — alongside 81 others — read 13 September 2026
We TON @weton · 20,260 Telegram ranks this channel #9 of 87 here — alongside 86 others — read 27 September 2026
@notyou @notyou · 46,401 Telegram ranks this channel #9 of 92 here — alongside 91 others — read 26 August 2026
DeDust.io RU – TON DEX @dedust_ru · 38,785 Telegram ranks this channel #12 of 85 here — alongside 84 others — read 30 August 2026
• by alenka • @alenkaontg · 21,090 Telegram ranks this channel #13 of 64 here — alongside 63 others — read 24 September 2026
Болтоши Болтомото @boltoshi · 50,006 Telegram ranks this channel #14 of 87 here — alongside 86 others — read 24 August 2026
Nemoneta.COM 🍿 @ne_moneta_com · 39,611 Telegram ranks this channel #17 of 82 here — alongside 81 others — read 29 August 2026
Bitpapa Media @bitpapa_io · 104,264 Telegram ranks this channel #19 of 47 here — alongside 46 others — read 21 September 2026
Your Premium | Your Notcoin @premium_not · 44,215 Telegram ranks this channel #22 of 77 here — alongside 76 others — read 27 August 2026
Risky Ventures hub @RiskSeeker · 20,624 Telegram ranks this channel #23 of 68 here — alongside 67 others — read 24 September 2026
Онтон | Крипта и IT @ontonbaton · 44,895 Telegram ranks this channel #25 of 85 here — alongside 84 others — read 27 August 2026
Крипта | ИИ Скруджа @Crypta_Ai · 25,756 Telegram ranks this channel #27 of 64 here — alongside 63 others — read 13 September 2026
Авторский Взгляд @vzglyadavtora · 42,020 Telegram ranks this channel #27 of 70 here — alongside 69 others — read 29 August 2026
Investment kingyru 💎 EN @investkingyru_en · 19,546 Telegram ranks this channel #28 of 80 here — alongside 79 others — read 30 September 2026
Sokolovsky inChain / биткоин и криптовалюты @sokolovskyinchain · 20,269 Telegram ranks this channel #33 of 81 here — alongside 80 others — read 28 September 2026
GURU KARTA INDONESIA @PendidikSDIndonesia · 88,640 Telegram ranks this channel #33 of 44 here — alongside 43 others — read 27 August 2026
Tribute | Монетизация контента @TributeNewsRU · 49,627 Telegram ranks this channel #33 of 78 here — alongside 77 others — read 25 August 2026
DOGG TON @doggton · 44,203 Telegram ranks this channel #34 of 85 here — alongside 84 others — read 27 August 2026
This channel appears in 84 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.
Domains linked from posts
27 domains 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 5 October 2026 — this
entry's latest reading, not the date you are reading this.
“рост будет бесконечный” (@tonbase), 1,493,931 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/tonbase.
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.
