Telegram RegisterThe public register of Telegram
Telegram profile photo for TON Status

Channel

TON Status

@tonstatus

Verified by Telegram

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

158,676subscribers

-5,441 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001744725639
TypeChannel
Username@tonstatus
DescriptionTechnical notifications and up-to-date requests for action for TON validators, developers and integrators. If you're a validator or developer of a popular TON service you should be subscribed.
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/tonstatus

Topic

Technology — 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 96% 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.

Growth

158,676164,117161,396.55 August 2026 — 164,117 subscribers6 August 2026 — 164,117 subscribers6 August 2026 — 164,029 subscribers7 August 2026 — 163,943 subscribers8 August 2026 — 163,800 subscribers9 August 2026 — 163,665 subscribers10 August 2026 — 163,550 subscribers11 August 2026 — 163,422 subscribers12 August 2026 — 163,271 subscribers13 August 2026 — 163,186 subscribers14 August 2026 — 163,069 subscribers15 August 2026 — 162,873 subscribers17 August 2026 — 162,696 subscribers18 August 2026 — 162,562 subscribers19 August 2026 — 162,418 subscribers20 August 2026 — 162,313 subscribers21 August 2026 — 162,135 subscribers22 August 2026 — 161,948 subscribers24 August 2026 — 161,670 subscribers25 August 2026 — 161,733 subscribers26 August 2026 — 161,638 subscribers27 August 2026 — 161,575 subscribers28 August 2026 — 161,472 subscribers29 August 2026 — 161,335 subscribers30 August 2026 — 161,243 subscribers31 August 2026 — 161,007 subscribers1 September 2026 — 160,832 subscribers2 September 2026 — 160,639 subscribers4 September 2026 — 160,431 subscribers6 September 2026 — 160,134 subscribers9 September 2026 — 159,712 subscribers11 September 2026 — 159,400 subscribers13 September 2026 — 159,080 subscribers15 September 2026 — 158,905 subscribers17 September 2026 — 158,676 subscribers5 August 202617 September 2026
35 measurements spanning 42 days, net -5,441. 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 157,860–164,933 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
17 Sept 2026, 05:40158,676-229
15 Sept 2026, 07:20158,905-175
13 Sept 2026, 18:16159,080-320
11 Sept 2026, 23:56159,400-312
9 Sept 2026, 12:37159,712-422
6 Sept 2026, 07:36160,134-297
4 Sept 2026, 03:58160,431-208
2 Sept 2026, 17:02160,639-193
1 Sept 2026, 13:54160,832-175
31 Aug 2026, 10:37161,007-236
30 Aug 2026, 07:57161,243-92
29 Aug 2026, 08:56161,335-137
28 Aug 2026, 08:53161,472-103
27 Aug 2026, 06:46161,575-63
26 Aug 2026, 09:23161,638-95
25 Aug 2026, 12:47161,733+63
24 Aug 2026, 13:28161,670-278
22 Aug 2026, 18:23161,948-187
21 Aug 2026, 09:44162,135-178
20 Aug 2026, 08:02162,313first reading

Engagement

27 posts held, back to 23 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 96 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.47%
avg views ÷ 158,676 subscribers
Avg views / post
8,690
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 27 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 27 August 2026
Posts held27 (23 May 202627 August 2026)
Views total26,060
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Sept 2026, 19:58 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

Links
156

Lifetime counters from Telegram’s own channel header, read 21 September 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.

Recent posts

27 Aug 2026, 15:01 UTC≈8,560 viewsread 21 September 2026

Attention Mainnet validators Please vote on the network configuration adjustment. Config 30: Increase the value of the leader_window parameter (and the associated leader_window_desync) to boost TPS by up to 30%. Config -123: Add the tg-wallet-v1 contract code to the network configuration. This contract is proposed for use with the native Gram Wallet on Telegram. If you use mytonctrl, please vote for proposals via

26 Aug 2026, 12:53 UTC≈8,280 viewsread 21 September 2026

Mainnet Validators Please schedule time tomorrow, August 27, at 15:00 UTC to participate in the vote on the mainnet configuration update. Voting is required.

24 Aug 2026, 15:19 UTC≈9,220 viewsread 21 September 2026

Attention Mainnet validators Please prepare for an increased network load and ensure that your validator nodes: 1) Have added a public collator list in accordance with the previously posted instructions. 2) Have a working QUIC port. Currently, validators with the following ADNL addresses do not have an operating QUIC port: 81A6ED816FE7C0552CA4CEDBC3BF4F2F03185CCD318CBF61DB06881D33C967CC 7ADCF5845D9878E3C21AA18C4

20 Aug 2026, 12:14 UTC≈8,090 viewsread 21 September 2026

Attention Mainnet validators This update is mandatory for validators; full node owners do not need to update. Please update mytonctrl software on your machines: update master Target versions: — mytonctrl: 64c2aa9 [v2.18.0] This step will complete activation of collators on Mainnet network. If you are not using mytonctrl, please add collators to your validators by downloading the default Mainnet collators list

18 Aug 2026, 12:35 UTC≈6,700 viewsread 21 September 2026

Attention Mainnet validators Please make sure that you have updated your machines to [2026.08] release and take part in the voting for network config adjustment: Config 29: Increase the maximum block size to fine-tune the performance of the collator's functionality. Config 31 and 46: Enable governance contracts related to the functionality of collators. If you use mytonctrl, please vote for proposal via vo 120975

17 Aug 2026, 14:00 UTC≈6,310 viewsread 21 September 2026

Mainnet Validator Software Update [v2026.08] This update is mandatory for validators; full node owners do not need to update. Please update your node software: Update with mytonctrl: upgrade master Target versions: — node: 3d478cb [v2026.08] If you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05). If you have several validators,

12 Aug 2026, 14:57 UTC≈6,200 viewsread 21 September 2026

Mainnet validators: Please schedule a time in accordance with the schedule outlined below to perform and activate the [2026.08] update. This update is mandatory for validators; full node owners do not need to update. The upcoming update will activate collators on the TON Mainnet network. Update schedule: Monday 17 August at 14:00 UTC: upgrade of node software to version [2026.08]. Tuesday 18 August at 12:30 UTC:

4 Aug 2026, 01:22 UTC≈7,920 viewsread 21 September 2026

Attention Mainnet validators Please take part in the voting for network config adjustment: Config 30: Set the protocol to stable version. If you use mytonctrl, please vote for proposal via vo 97476904964537115993827662219965215594287692635916428067774379550074503377880

3 Aug 2026, 12:51 UTC≈7,650 viewsread 21 September 2026

Mainnet Validator and Node Software Update [v2026.07] Please update your node software: Update with mytonctrl: update master upgrade master reload_global_config Target versions: — node: bb935a8 [v2026.07] — mytonctrl: 90046e0 [v2.17.1] If you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05). If you have several validators, pleas

3 Aug 2026, 10:57 UTC≈5,630 viewsread 21 September 2026

The update instructions will be published within 2 hours.

30 Jul 2026, 06:57 UTC≈8,060 viewsread 21 September 2026

Mainnet validators and node owners: Please schedule a time on Monday 3 August at 11:00 UTC to perform the software update. This update is mandatory for both validators and full node owners. The update will complete the switch to the plumtree broadcast method enabled in release 2026.06, and will disable the legacy broadcast method to reduce network traffic.

23 Jul 2026, 12:23 UTC≈10,800 viewsread 21 September 2026

Mainnet node owners Please update your nodes to the 2026.06 release now. See https://t.me/tonstatus/225. Failure to update your nodes will result in loss of network synchronization once legacy broadcasts are disabled in approximately one week.

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

Forward network

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

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.

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.

TON Dev News
@tondev_news · 41,092
#1
Anatoly Makosov
@anatoly_makosov · 42,515
#2
Gram of TON
@gram · 6,689,636
#3
The Daily TON | News
@thedailyton · 256,828
#4
Notcoin Community
@notcoin · 8,643,687
#5
Wallet News
@cryptowallet_news_en · 3,531,077
#6
TON Community
@toncommunitychannel · 765,782
#7
Ton Post
@tonpost · 72,912
#8
HOT Updates
@hotonnear · 4,675,152
#9
Keeper News
@keeper_en · 4,754,957
#10
tapswap community
@tapswapai · 10,368,717
#11
Time Farm News
@TimeFarmChannel · 5,296,110
#12
Dotcoin Community
@dotcoincommunity · 3,977,366
#13
Nomis | Onchain Reputation Protocol
@nomis_protocol · 1,549,523
#14
WATCoin
@watbird · 1,476,557
#15
STON.fi
@stonfidex · 736,298
#16
TonRadar
@tonradarapp · 53,337
#17
Alex Falcon
@iamalexfalcon · 3,088,378
#18
Aqua Protocol - Borrowing on TON (EN)
@aquaprotocolxyzchannelen · 767,036
#19
TON POINTER ENG
@TONPOINTEReng · 539,702
#20
Tonstakers
@thetonstakers · 908,245
#21
DOGS Community
@dogs · 7,065,215
#22
TonDreamer Eng
@TonDreamerEng · 735,160
#23
Hamster Kombat Announcement
@hamster_kombat · 20,982,519
#24
Blum: All Crypto – One App
@blumcrypto · 14,360,001
#25
TON Jobs
@tonhunt · 65,478
#26
Builders
@builders · 3,431,951
#27
Catizen Announcement
@catizenann · 3,581,173
#28
Yescoin
@theyescoin · 5,697,036
#29
Trending Apps
@trendingapps · 3,812,897
#30
Catapult Extreme
@catapult_extreme · 8,500,526
#31
Tomarket Announcement
@tomarket_ai · 6,657,802
#32
SEED Updates
@seedupdates · 8,226,508
#33
CashFlow‘s Calls
@CashFlowsCalls · 508,677
#34
FX Holding | Official
@fx_holding_community · 6,083,788
#35
Gram RUS
@toncoin_rus · 526,912
#36
CATS Community
@Cats_housewtf · 7,949,411
#37
GAMEE Community
@gameechannel · 1,901,951
#38
Boom: Crypto News
@boomloudcoin · 1,671,644
#39
Investment kingyru 💎
@investkingyru · 1,728,086
#40
Анатолий Макосов
@anatolii_makosov · 18,049
#41
PocketFi News
@pocketfi · 1,799,855
#42
Bitget Wallet Announcements
@Bitget_Wallet_Announcement · 3,968,612
#43
HEXN.IO Channel
@hexnio · 1,998,607
#44
CEX.IO's Official Community Channel
@CEXIO_Announcements · 2,498,015
#45
Новости Кошелька
@cryptowallet_news_cis · 1,128,418
#46
the noton
@thenoton · 711,502
#47
GOATS Channel
@realgoats_channel · 4,674,136
#48
Vertus Announcements
@the_vertus · 2,149,775
#49
The Daily TON | Новости
@thedailytonrus · 70,194
#50
Leagues of the World
@league · 1,002,238
#51
Yescoin Foundation
@therealyescoin · 2,089,882
#52
Медиа Россия
@mediarussia · 1,694,028
#53
Banana Announcement
@banana_update · 1,401,181
#54
Cryptozon
@monorixofficial · 1,336,669
#55
Binance Announcements
@binance_announcements · 3,456,487
#56
1win Token
@token_1win · 2,980,801
#57
TapCoins
@theTapCoins · 2,919,608
#58
Pixelverse.xyz News Channel
@pixelverse_xyz · 3,136,037
#59
Дайте TON!
@givemetonru · 2,089,622
#60
Rocky Rabbit Channel
@rockyrabbitio · 3,502,824
#61
PIGS Community
@pigscrew · 2,142,006
#62
Deep Ton
@DeepTon · 19,495
#63
ANON
@anon_club · 354,189
#64
AVACOIN Channel
@avagoldcoin · 1,753,173
#65
Holdcoin Channel
@Holdcoin_Channel · 2,182,616
#66
Meta Silense TON
@ToNmetasilense · 2,762,588
#67
DeCenter — блокчейн, биткоин, инвестиции
@DeCenter · 1,823,722
#68
HAYZON
@hayzonn · 2,830,164
#69
Cat Gold Miner Announcements
@catgoldminerann · 904,797
#70
TON Station
@tonstationgames · 3,193,102
#71
TON CIS Hub
@toncishub · 31,282
#72
Storm Trade | News ⚡️
@storm_trade_news · 914,189
#73
We TON
@weton · 20,494
#74
AM Community
@AmioCommunity · 1,747,054
#75
Getgems NFT
@getgems · 271,478
#76
Новости Keeper
@keeper_cis · 458,130
#77
Money 💰 Crypto & Finance
@money · 2,974,351
#78
Roxman
@roxman · 7,057,063
#79
Simple Wallet
@smpl_app · 1,619,786
#80
Crypto Wolf
@Crypto_Woolf · 2,191,483
#81
ONUS Announcements (English)
@onus_globalchannel · 1,650,302
#82
TON PIZ
@tonpizdev · 3,352
#83
Corn Battles🌽⚔️🌽
@corn_battles · 1,045,929
#84
🦄 Max.ton
@gramlow · 22,563
#85
Telegram Tips
@telegramtips · 10,963,130
#86
Новости Crypto Bot
@cryptobotru · 2,327,822
#87
Full Metal Jetton
@full_metal_jetton · 42,823
#88

Read from Telegram’s recommendation API, most recently 12 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 Dev News
@tondev_news · 41,092
Telegram ranks this channel #1 of 87 here — alongside 86 others — read 29 August 2026
TON Tech
@tontech · 24,328
Telegram ranks this channel #3 of 49 here — alongside 48 others — read 16 September 2026
Anatoly Makosov
@anatoly_makosov · 42,515
Telegram ranks this channel #3 of 81 here — alongside 80 others — read 28 August 2026
The Open Network
@tonblockchain · 187,913
Telegram ranks this channel #8 of 75 here — alongside 74 others — read 20 August 2026
TON Jobs
@tonhunt · 65,478
Telegram ranks this channel #19 of 92 here — alongside 91 others — read 21 August 2026
JAY SPORTS 🏀 🎯 🎾
@jaysportsplug · 54,203
Telegram ranks this channel #24 of 24 here — alongside 23 others — read 22 August 2026
Ton Post
@tonpost · 72,912
Telegram ranks this channel #26 of 89 here — alongside 88 others — read 19 August 2026
Tonnel Network
@tonnel_en · 177,784
Telegram ranks this channel #28 of 80 here — alongside 79 others — read 30 August 2026
Kirill Malev
@kirill_malev · 23,841
Telegram ranks this channel #29 of 81 here — alongside 80 others — read 17 September 2026
जिद्द खाकी वर्दीचीच🧑🏻‍✈️
@jidd_khaki_vardichich · 24,774
Telegram ranks this channel #33 of 57 here — alongside 56 others — read 15 September 2026
Oga Amos
@ogaamosofafrica · 35,860
Telegram ranks this channel #34 of 56 here — alongside 55 others — read 1 September 2026
Telegram Contests
@contest · 299,058
Telegram ranks this channel #38 of 78 here — alongside 77 others — read 20 August 2026
PixelSwap
@PixelSwap_io · 508,931
Telegram ranks this channel #44 of 85 here — alongside 84 others — read 27 August 2026
TON Contests
@toncontests · 128,696
Telegram ranks this channel #44 of 73 here — alongside 72 others — read 20 August 2026
<\> Sharding, TON's, two Jetons </>.
@ton2keng · 597,907
Telegram ranks this channel #45 of 89 here — alongside 88 others — read 17 August 2026
BotNews
@BotNews · 131,414
Telegram ranks this channel #48 of 65 here — alongside 64 others — read 20 August 2026
Forward Protocol
@ForwardProtocol · 45,639
Telegram ranks this channel #53 of 80 here — alongside 79 others — read 27 August 2026
TonRadar
@tonradarapp · 53,337
Telegram ranks this channel #53 of 92 here — alongside 91 others — read 23 August 2026
Shardify | by Meridian
@shardify · 23,344
Telegram ranks this channel #55 of 78 here — alongside 77 others — read 18 September 2026
TON Community
@toncommunitychannel · 765,782
Telegram ranks this channel #57 of 84 here — alongside 83 others — read 8 August 2026
DeDust.io – TON DEX
@dedust_en · 68,225
Telegram ranks this channel #60 of 84 here — alongside 83 others — read 20 August 2026
TON Hedge News
@ton_hedge · 38,003
Telegram ranks this channel #61 of 85 here — alongside 84 others — read 31 August 2026
Daily Telegram
@daily_telegram · 36,010
Telegram ranks this channel #63 of 65 here — alongside 64 others — read 1 September 2026
Codyfight Announcements
@codyfightnews · 49,113
Telegram ranks this channel #64 of 91 here — alongside 90 others — read 25 August 2026

This channel appears in 49 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.

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

“TON Status” (@tonstatus), 158,676 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/tonstatus.

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.