Telegram RegisterThe public register of Telegram

Channel

TON Official NODE

@TonOfficialNode

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

2,742subscribers

-7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002276870589
TypeChannel
Username@TonOfficialNode
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/TonOfficialNode

Topic

Crypto & trading — 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 67% 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. 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
@TON_Official_Node/106820 Feb 2026, 11:29 UTC@TonOfficialNode/1318 · this entry22 Feb 2026, 20:56 UTC1.002 days
@TON_Official_Node/107426 Feb 2026, 12:17 UTC@TonOfficialNode/1322 · this entry27 Feb 2026, 11:01 UTC1.0023 hours
@TonOfficialNode/1329 · this entry31 Mar 2026, 12:50 UTC@TON_Official_Node/110213 Apr 2026, 11:53 UTC1.0013 days
@TON_Official_Node/110430 Apr 2026, 09:47 UTC@TonOfficialNode/1331 · this entry30 Apr 2026, 09:48 UTC1.0072 seconds
@TonOfficialNode/1333 · this entry16 May 2026, 11:54 UTC@TON_Official_Node/110616 May 2026, 12:18 UTC1.0024 minutes
@TonOfficialNode/1334 · this entry19 May 2026, 10:07 UTC@TON_Official_Node/110719 May 2026, 10:08 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@TON_Official_Node15 (8/8 hand-verifiable sample passed)1.0024 minutesthis entry (105)

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 5 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 20 comparable posts for this entry, running 22 February 2026 to 6 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 2, the earliest publisher we hold is @TON_Official_Node. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 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 1 other registered channel, 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

2,7422,7532,747.57 August 2026 — 2,749 subscribers7 August 2026 — 2,749 subscribers8 August 2026 — 2,753 subscribers11 August 2026 — 2,742 subscribers7 August 202611 August 2026
4 measurements spanning 3 days, net -7. 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 2,740–2,755 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 06:422,742-11
8 Aug 2026, 05:502,753+4
7 Aug 2026, 20:022,749no change
7 Aug 2026, 19:282,749first reading

Engagement

20 posts held, back to 22 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
37.2%
avg views ÷ 2,742 subscribers
Avg views / post
1,020
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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 6 August 2026
Posts held20 (22 February 20266 August 2026)
Views total1,020
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 20:02 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
4m 08s
Average length
1m 23s

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.

Recent posts

6 Aug 2026, 08:11 UTC≈1,020 viewsread 7 August 2026
Photo

⚙️ Automated health checks & failover — TON Official Node continuously monitors node status, performance, and connectivity to ensure stable operation. When an anomaly is detected, the system executes a structured response: automated restart, role redistribution across redundant peers, and state resynchronization. These actions are fully automated and do not require or access user wallets or private keys. This layer

5 Jul 2026, 10:01 UTC≈2,170 viewsread 7 August 2026
Video

📹 Video Guide: How to Connect to TON Official Node 💎 A step-by-step connection guide is now available. The tutorial is demonstrated using Bybit, an official partner exchange of TON Official Node. The same participation process can be completed by following the instructions shown in the video. The guide covers each stage of the connection process in a clear and structured format to help participants complete their

15 Jun 2026, 12:06 UTC≈8,800 viewsread 7 August 2026
Photo

🚨 TONcoin Rebranding to GRAM The TON token is being rebranded and will continue under the new ticker GRAM. ⚙️ Important: this change applies to the token ticker only. The TON blockchain and its ecosystem continue to operate normally. Binance 📅 June 30, 2026 at 03:30 UTC TON deposits and withdrawals will be suspended. 📅 July 2, 2026 at 07:00 UTC GRAM deposits and withdrawals will become available. After the migr

1 Jun 2026, 11:54 UTC≈8,680 viewsread 7 August 2026
Photo

⚙️ TON Official Node System Update As part of measures to optimise the infrastructure and distribute the network load, the following updates are being introduced: From now on, the following is available per account: 🔄 up to 5 transactions per day This change is being implemented to: • ensure more stable operation of TON nodes • distribute network load correctly • maintain high transaction processing speeds • ens

1 Jun 2026, 06:57 UTC≈2,790 viewsread 7 August 2026
Photo

🌐 20% off any eSIM on TonMobile for Tonkeeper users Summer is the season of travel, spontaneous plans, and new adventures. To keep you connected anywhere in the world without roaming, we’ve teamed up with TonMobile to bring a special gift for Tonkeeper users. Use a one-time promo code for 20% off any eSIM: SUMMERTON26 The promo code is valid until the end of June. How to use it: 1️⃣ Open TonMobile via the Tonkee

19 May 2026, 15:05 UTC≈9,980 viewsread 7 August 2026
Photo

⚙️ Dear TON Official Node participants, Technical work to expand and optimize the infrastructure has been successfully completed ✅ The system is now back to normal operation, and all core TON Official Node services and features are available without restrictions. The following improvements were made during the update: • network stability • transaction processing speed • data synchronization • overall infrastructur

19 May 2026, 10:07 UTC≈2,840 viewsread 7 August 2026
Photo

⚙️ Dear TON Official Node participants Due to the rapid increase in the number of connections and the high load on the infrastructure, technical work is currently underway to expand the network’s capacity. At present, the app may be temporarily unavailable to some users. The work is aimed at improving the stability, processing speed and scalability of TON Official Node 🚀 The technical team is already carrying out

16 May 2026, 11:54 UTC≈1,850 viewsread 7 August 2026
Photo

🔒 Security Boundary in TON Official NODE TON Official NODE is designed as an infrastructure access system, not as a wallet or asset custody service. The platform does not store user funds, does not manage private wallets, and does not require seed phrases or passwords. Participation is structured through the application: users follow the setup logic, save their return address, and monitor activity through the inter

5 May 2026, 20:05 UTC≈2,070 viewsread 7 August 2026
Photo

🚀 TON Official NODE — Updates and Project Development The project continues to develop actively. The team has implemented a number of improvements aimed at enhancing stability, speed, and user-friendliness. What's New: ⚙️ Transaction processing has been optimized — the system runs faster and more reliably 🔄 Data synchronization between nodes has been improved 📊 Activity and transaction history display has been upd

30 Apr 2026, 09:48 UTC≈1,970 viewsread 7 August 2026
Photo

The TON Official Node is designed to simplify access to the TON network infrastructure. Our system automates complex technical processes, allowing participants to contribute to the ecosystem without requiring advanced technical knowledge. The platform autonomously manages key aspects of node operation, including: • Step-by-step initial setup and deployment. • Continuous monitoring of performance and process status.

15 Apr 2026, 16:23 UTC≈10,700 viewsread 7 August 2026
Photo

TON Official NODE: Network Scaling Analysis The infrastructure has recorded an 18% increase in active participation over the last 72 hours. Current metrics indicate a steady expansion of the distributed network. 📊 Key System Metrics: • Total active participants: 42358 • Transactions processed (7-day period): 315240 • Average system synchronization: 100% Technical performance remains stable as the architecture sca

31 Mar 2026, 12:50 UTC≈29,500 viewsread 7 August 2026
Photo

📊 Official TON Node — Updated Project Statistics Over the past few days, the system has shown steady growth in activity. Below are the latest node performance metrics: ✅ Number of transactions processed on the TON network: 250,000+ ✅ Active users: 30,000+ We continue to develop the infrastructure of the official TON node — optimizing processing speed, expanding functionality, and improving user interaction with th

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

Mentions

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

“TON Official NODE” (@TonOfficialNode), 2,742 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/TonOfficialNode.

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.