Channel
@next_ton_pool
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
3,835subscribers
-73 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001714912791 |
|---|---|
| Type | Channel |
| Username | @next_ton_pool |
| Created | Between 1 December 2021 and 22 February 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/next_ton_pool |
Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 20:40 | 3,835 | -8 |
| 2 Oct 2026, 03:39 | 3,843 | -23 |
| 12 Sept 2026, 16:18 | 3,866 | -6 |
| 8 Sept 2026, 07:37 | 3,872 | -7 |
| 3 Sept 2026, 01:09 | 3,879 | -2 |
| 30 Aug 2026, 21:07 | 3,881 | -2 |
| 27 Aug 2026, 15:37 | 3,883 | -3 |
| 24 Aug 2026, 05:58 | 3,886 | -7 |
| 20 Aug 2026, 12:33 | 3,893 | -5 |
| 17 Aug 2026, 17:47 | 3,898 | -3 |
| 14 Aug 2026, 14:16 | 3,901 | -4 |
| 11 Aug 2026, 00:16 | 3,905 | -3 |
| 7 Aug 2026, 03:30 | 3,908 | no change |
| 7 Aug 2026, 03:20 | 3,908 | first reading |
20 posts held, back to 22 February 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pages of 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 20 posts for this entry, the most recent from 1 July 2022. An engagement rate over an empty window would be a number about nothing.
All balances have been paid out, and the chat is muted to prevent spam. For any other questions, please contact https://t.me/next_ton_pool_supportbot within 14 days (before July 15). We will not answer any questions beyond that date.
TON mining is over. Thanks for your support! Refer to the last message for details. Make sure to switch your miner to ETH-only mode to avoid reconnections.
Please note that the estimated time for giver depletion has been adjusted to June 26th June 27th, and will continually be adjusted according to the circumstances. Until all giver depletes, the pool will remain online.
The pool is working. Please restart your miner if connectivity is not restored.
Due to Cloudflare outage, users may experience issues connecting to our servers in certain regions. The status can be viewed at https://www.cloudflarestatus.com/. We are monitoring the situation closely, and mining will continue as soon as the problem is fixed.
Giver depletion is expected to happen after June 22nd (latest estimate: June 26th June 27th). Here is the plan for pool shutdown: 1. Once givers are depleted, we will shut down all mining servers, including next.ton-pool.com and all stratum servers. Depending on your mining software and whatever watchdog you are using, you may experience mining software restarts affecting other coins you're mining, so make sure to sw…
hk1.stratum.ton-pool.com experienced a partial outage in the last hours. It is back to normal now. Some miners may see reduced hashrate from the bot, but rest assured that the profit was not affected and would be accrued like normal even if the bot displayed a hashrate of 0 at the time.
We unfortunately have some sad news to share: TON coins in givers are getting close to depletion. Giver 1 has the lowest balance and will deplete very soon, and other 9 givers will deplete one by one in the following days. Once the giver balances run out, no more TON can be mined and the pool will shut down. You can check the balances of all givers at https://ton.org/mining/ to get an idea of how many days there are …
In case you haven't noticed yet, recently a 100% LHR unlock was published for ETH mining. Many of our miners using LHR cards fled to mine ETH. But there's more! lolMiner and GMiner supports not only full LHR unlock but also ETH-TON dual mining. Both Linux and Windows are supported. Check them out if you haven't yet.
We have applied a fix and hashrate stats should go back to normal now. Note that since hashrate during the downtime was not counted, the 24hr and 1hr hashrate may remain lower than actual for some time. Thanks for your understanding!
The pool currently has some technical problems and the hashrate reported by the bot may be inaccurate. Mining is unaffected and the profit will accrue as normal. Please bear with us while we're investigating the issue. Thanks!
There was a delay in withdrawals in the last hour. Our pool operators are working on the issue, and withdrawals should be resumed now. You can check our homepage at https://ton-pool.com/#status. Under the "Status" section there are three numbers indicating the status of withdrawal queue, such as: Withdrawals: 103 pending, 24 processing, 712192 done When the number of pending and processing withdrawals are high, it me…
Showing the 12 most recent of 20 posts we hold for @next_ton_pool. 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.
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.
@next_ton_pool named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“TON-Pool News” (@next_ton_pool), 3,835 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/next_ton_pool.
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.