17 measurements spanning 16 days, net -95. 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 12,074–12,197 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
21 Aug 2026, 15:17
12,088
-9
20 Aug 2026, 14:27
12,097
-4
19 Aug 2026, 13:57
12,101
-21
18 Aug 2026, 15:33
12,122
-17
17 Aug 2026, 17:28
12,139
-14
16 Aug 2026, 14:15
12,153
-6
15 Aug 2026, 00:25
12,159
-5
13 Aug 2026, 16:48
12,164
+1
12 Aug 2026, 17:44
12,163
-9
11 Aug 2026, 16:33
12,172
+3
10 Aug 2026, 15:23
12,169
+2
9 Aug 2026, 14:14
12,167
-2
8 Aug 2026, 15:22
12,169
-9
7 Aug 2026, 16:53
12,178
-4
6 Aug 2026, 17:00
12,182
-1
6 Aug 2026, 02:34
12,183
no change
6 Aug 2026, 00:48
12,183
first reading
Engagement
22 posts held, back to 21 February 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 27 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
4.68%
avg views ÷ 12,088 subscribers
Avg views / post
566
2 posts measured
Reaction rate
1.06%
reactions ÷ views · ER floor
Posts in window
2
of 22 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 18 August 2026
Posts held
22 (21 February 2025 – 18 August 2026)
Views total
1,132
Reactions total
12
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Aug 2026, 14:25 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
13
Links
39
Lifetime counters from Telegram’s own channel header, read 22 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.
Reaction mix
933 reactions across 22 posts, in 24 distinct kinds. The most used accounts for 33.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
315
33.8%
👍
272
29.2%
🔥
203
21.8%
👏
25
2.68%
✍
20
2.14%
💩
17
1.82%
🐳
10
1.07%
👎
10
1.07%
👌
9
0.965%
👀
8
0.857%
😁
8
0.857%
🕊
6
0.643%
❤🔥
4
0.429%
🎉
4
0.429%
😢
4
0.429%
🍾
3
0.322%
🏆
3
0.322%
👾
3
0.322%
🗿
3
0.322%
🌚
2
0.214%
4 further kinds
4
0.429%
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 22 of the 22 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 933reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 21 February 2025 to 18 August 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.
❗️`/v2/jettons/{addr}/holders` got pagination upgrade. offset parameter will be limited soon.
GetJettonHolders method was always returning holders sorted by their balance (starting from the top). It also had offset parameter that users can use to traverse the top 10k holders.
This approach has two problems:
1) inconsistency. Obviously, balances change constantly. So scanning data with limit+offset will get a lot of…
How to get all jettons? And what's changing in TONAPI?
In a nutshell
There are two main ways: TONAPI (the /v2/jettons method) and Tonconsole.com (CSV export).
When using the /v2/jettons method for pagination, it's recommended to use the cursor — the last_account_id parameter, which is taken from the previous response. It looks something like this:
% curl -s 'https://tonapi.io/v2/jettons?limit=10' | jq -r '.jettons |…
Toncoin → Gram
Following the approved network changes, TONAPI and Tonviewer now support the new currency naming: Gram.
We have made every effort to preserve backward compatibility wherever possible.
List of Changes
1. Both Variants Are Accepted in Input Parameters
The /v2/rates/chart endpoint now supports a new currency value:
* https://tonapi.io/v2/rates/chart?token=usdt¤cy=ton&points_count=5
* https://t…
Help up become better.
We want to make TON Console better and more useful for everyone, and we’re currently collecting some feedback from users.
If you’ve used the console, we’d love to hear:
- what you like about it
- what feels confusing or inconvenient
- what features you think are missing
You can share your feedback through this short form
or just leave a comment under this post.
Any thoughts or suggestions w…
🚀 Billing Update: USDT Top-Ups
We’ve rolled out an update that makes USDT the primary way to top up your balance and pay for services in TON Console.
What’s new
• Top up in USDT and pay for services in USDT
• Improved charge history with CSV export
• Multiple UX improvements across the Console
📝 TON top-ups will still be available only for projects with an existing TON balance at the time of the update.. Also, cha…
⚠️ Planned TON Console Update
When: 16 Feb, 06:30–08:30 UTC
Impact: Console may be unavailable for up to 2 hours during this window.
Services: Your products and APIs will continue running normally (no downtime expected).
Please plan accordingly — you won’t be able to access Console to manage products while the migration is in progress
Help us become better.
You probably use tonviewer.com, and you likely have ideas on how it could be improved or fixed. We’d really appreciate it if you took our survey and helped us make it better.
Alternatively, you can share your feedback directly in the comments under this post.
Dear users,
Please note that on October 20, the liteserver error codes in the service at https://tonconsole.com/tonapi/liteservers will be updated.
Alongside the standard liteserver error codes (such as 651, -400, etc.), the service may return additional codes.
Specifically, error code 5556 will be REPLACED with 228 (rate limit exceeded) for consistency.
Proper handling of these error codes is crucial for maintainin…
We plan maintenance work today at 14:00 UTC for approximately less than an hour. The tonconsole.com admin panel and analytics queries may be unavailable during this time. The functionality of the main API will not be affected.
Technical update about external messages for wallets v4
Tomorrow ~10:00 UTC we will deploy an emergency update that breaks backward compatibility. The decoded external message body for wallets_v4r2 will now use a SumType for the payload.
You can see the difference at the following two URLs:
https://dev.tonapi.io/v2/blockchain/transactions/3d3ad440cd5d1c5bb089695338f250d19707659e4444c98756fcc0d444558346 - new versio…
❤26👍15😁5👏4👌3🔥3
Signed Denis Subbotin
Showing the 12 most recent of 22 posts we hold for @tonconsole_com. 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 — 322,374 of 1,581,209entries 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 5 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.
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.
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.
The Open Network @tonblockchain · 190,859 Telegram ranks this channel #18 of 75 here — alongside 74 others — read 20 August 2026
DeDust.io – TON DEX @dedust_en · 69,756 Telegram ranks this channel #43 of 84 here — alongside 83 others — read 20 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. 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 21 August 2026 — this
entry's latest reading, not the date you are reading this.
“TONAPI and TON Console” (@tonconsole_com), 12,088 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/tonconsole_com.
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.