Telegram RegisterThe public register of Telegram

Channel

TON Starter

@tonstarter

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

8,054subscribers

-18 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001690792791
TypeChannel
Username@tonstarter
DescriptionКанал проекта @tonbase. Здесь будут публиковаться проекты экосистемы TON. Для связи: @highfeed (NFT не публикую).
CreatedBetween 1 December 2021 and 14 February 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/tonstarter

Topic

Giveaways & airdrops — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 48% 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 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@tonstarter/12 · this entry29 Jul 2022, 09:26 UTC@tonbase/28529 Jul 2022, 09:40 UTC1.0014 minutes
@tonstarter/22 · this entry28 Jan 2024, 15:43 UTC@tonbase/47528 Jan 2024, 15:43 UTC1.00under a minute
@tonbase/7571 Nov 2024, 14:27 UTC@tonstarter/23 · this entry2 Nov 2024, 16:03 UTC1.0026 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@tonbase5 (5/5 hand-verifiable sample passed)1.00under a minute@tonbase (32)

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 2 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 14 comparable posts for this entry, running 19 February 2022 to 2 November 2024. 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 key 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.

Growth

8,0548,0728,0636 August 2026 — 8,072 subscribers6 August 2026 — 8,072 subscribers6 August 2026 — 8,070 subscribers9 August 2026 — 8,064 subscribers11 August 2026 — 8,054 subscribers6 August 202611 August 2026
5 measurements spanning 6 days, net -18. 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 8,051–8,075 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 23:158,054-10
9 Aug 2026, 05:528,064-6
6 Aug 2026, 13:028,070-2
6 Aug 2026, 03:048,072no change
6 Aug 2026, 00:488,072first reading

Engagement

18 posts held, back to 14 February 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pagesof 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 2 November 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
13
Videos
4
Links
16

Lifetime counters from Telegram’s own channel header, read 12 August 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
1m 06s
Average length
17s

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.

Recent posts

2 Nov 2024, 16:03 UTC≈6,250 viewsread 12 August 2026
Photo

Ситуация в TON в день конференции разделилась на два лагеря: Одни делают анонсы анонсов на конференции. А другие запускают релизы без посещения конфы и выступления там: - 😺 Tonscan.org запустил страницу маркета жетонов – t.me/catchain/90 - 🐠 MyTonWallet интегрировал MoonPay – t.me/MyTonWalletRu/161 - 🤖 Crypto Bot запустили обмены и конкурс на $10,000 - t.me/CryptoBotRU/367

28 Jan 2024, 15:43 UTC≈42,500 viewsread 12 August 2026
Photo

🎁 Розыгрыш 🐬 100 TON ($211.23) 10 победителей разделят 🐬 100 TON, каждый получит по 🐬 10 TON ($21.12). Подпишитесь на каналы и нажмите кнопку «Принять участие», чтобы стать участником розыгрыша: 1. TON Base 2. TON Starter 04 февр. 2024 в 16:00 🦋 Crypto Bot выберет победителей случайным образом.

6 Oct 2023, 14:35 UTC≈38,200 viewsread 12 August 2026
Video

👛Кошелёк MyTonWallet получил большое обновление! Обновленный дизайн, управление токенами, зашифрованные сообщения и многое другое. Подробнее читайте в их большом анонсе.

23 Jun 2023, 17:59 UTC≈26,200 viewsread 12 August 2026
Forwarded from @MyWalletRusVideo

🔥 Горячие новости от MyTonWallet 🔥 Сегодня знаменательный момент на нашем пути развития! Мы рады и горды объявить о запуске новой 14 версии, в которой представлен ряд важных улучшений, которые делают работу с MyTonWallet еще более удобной и безопасной. Итак, к обновлениям: 1️⃣ Полноценная версия для ПК: mytonwallet.app/get MyTonWallet становится первым кошельком TON, который предлагает версии для Windows, macOS и

7 Apr 2023, 08:36 UTC≈9,690 viewsread 12 August 2026
Photo

🆕 У моего флагманского проекта @TONNotifyBot вышло грандиозное обновление: • Комментарии. Теперь для адресов можно указать какие комментарии нужно отслеживать, а какие наоборот исключить. Можете теперь безнаказанно следить за теми, кто сливает любимые тончики на биржах. • Минимальная сумма. Появилась возможность указать минимальную сумму от которой будут приходить уведомления. • Новый синхронизатор. Обновили с

13 Jan 2023, 12:58 UTC≈7,820 viewsread 12 August 2026
Forwarded from @MyWalletRusVideo

🏦 Первый нативный стейкинг MyTonWallet становится первым кошельком, предоставляющим стейкинг на официальном смарт-контракте. Стейкинг полностью децентрализован и управляется официальным смарт-контрактом TON Nominator. Ни разработчики, ни кто-либо ещё не имеет доступа к средствам на вашем депозите. Зарезервированные средства используются для поддержания работы сети в рамках её основного механизма proof-of-stake. Пр

6 Dec 2022, 17:29 UTC≈7,290 viewsread 12 August 2026
Photo

👛 MyTonWallet – один из лучших кошельков и браузерное расширение для блокчейна TON. Красивый и удобный интерфейс, в совокупности с поддержкой жетонов и мульти-кошельков позволяет в полной мере пользоваться возможностями блокчейна TON в любой момент. mytonwallet.app – веб-кошелёк, доступен на любом устройстве. mytonwallet.io – расширение для Chrome. Канал с новостями и исходный код на GitHub.

6 Dec 2022, 17:21 UTC≈7,800 viewsread 12 August 2026
Photo

💱 Fragment.com – место, где вы можете купить или продать Telegram Username используя монету TON.

4 Aug 2022, 12:52 UTC≈10,300 viewsread 12 August 2026
Photo

@TONNotifyBot – этот бот присылает уведомления, когда по добавленным адресам TON происходит движение монет.

29 Jul 2022, 09:26 UTC≈11,100 viewsread 12 August 2026

​Мультичек на 100 TON ($89.80). Сумма одного чека: 0.1 TON ($0.09) Количество активаций: 1,000 💬 Проверка чека только для пользователей с Telegram Premium.

29 Jul 2022, 09:26 UTC≈7,510 viewsread 12 August 2026
Video

Сервис @CryptoBot получил важные обновления на этой неделе: 1. Была добавлена сеть TRON (TRC20) для монеты USDT. 2. Подведены итоги первой половины 2022 года. 3. Добавлена сеть Ethereum и монета ETH. 4. Добавлена опция включения активации чеков только для пользователей с Telegram Premium. 5. Снижена комиссия на бирже для всех пар. Для тейкеров – 0.75%, для мейкеров – 0.5%.

21 Jul 2022, 06:03 UTC≈8,460 viewsread 12 August 2026
Photo

Конструктор ботов puzzlebot.top интегрировал платежную систему Crypto Pay от @CryptoBot в свои сервисы.

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

Citation-graph rank

Citation-graph rank — 176,175 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 2 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.

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

“TON Starter” (@tonstarter), 8,054 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/tonstarter.

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.