5 measurements spanning 23 days. 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 79–82 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
30 Aug 2026, 18:13
81
+2
14 Aug 2026, 14:34
79
-3
9 Aug 2026, 18:16
82
no change
7 Aug 2026, 22:08
82
+1
7 Aug 2026, 20:13
81
first reading
Engagement
8 posts held, back to 29 March 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 8 posts for this entry, the most recent from 3 May 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
36 reactions across 7 posts, in 9 distinct kinds. The most used accounts for 27.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
10
27.8%
👍
7
19.4%
❤🔥
5
13.9%
🆒
5
13.9%
🫡
4
11.1%
💯
2
5.56%
⚡
1
2.78%
👏
1
2.78%
🥰
1
2.78%
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 7 of the 8 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 29 March 2024 to 3 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
apiTON does NOT have an official token. Be vigilant ⚠️:
- A fraudulent token named "API" was created ~1 hour ago to mislead the community.
- Do NOT interact with this token or any links promoting it.
How to Verify:
1. Check the token via @apitonBot
(you can do it in any chat, just type @apitonBot [your query])
2. Notice the red flags:
- Token metadata uses public image hosting, not a dedicated domain.
- No of…
What you can do with @apitonBot:
💬 1. Use Inline Queries
Just type, for example: @apitonBot @anime in ANY Chat.
Get answer immediately!
🔍 2. Find TON Addresses & Owners by Telegram @username
Instantly uncover the TON blockchain address and owner details linked to NFT Telegram username.
📱 3. Look Up TON address and owner by +888 number
Enter NFT number like at photo to reveal its associated TON address and owner
…
Update Released for @apitonBot:
[ What's New ]
📊 Auction / Sale Data for Any NFT Contract
You can now view auction and sale data for any NFT contract. This will help you better analyze market activity.
🖼 Displaying Images for Contracts
Images have been added to each contract implemented in compliance with the community standards TEP-64 (Token Data Standard) and TEP-74 (Jettons Standard). This make…
Hey there, crypto enthusiasts! 👋 Let’s talk about Compressed
NFTs (cNFTs) on the TON Blockchain and why they’re
bridging the gap between Web 2.0 and Web 3.0! 🤩
What are Compressed NFTs (cNFTs)? 🤔
Compressed NFTs (cNFTs) are smaller, cheaper, and faster
versions of traditional NFTs! 💸💨 By using data compression,
cNFTs reduce storage and transaction costs, making them super
efficient while keeping all the cool featur…
If you know that everything you do wrong isn't a secret to others, will you still do that?
I know you're a good person who sees a lot of bad things.
From today, you can do less for scammers. Just use @apitonBot to check your new contacts by @username or 888 number, and everything will be fine.
However, it's highly recommended not to open links to deals, even if they look familiar and trustworthy.
There are severa…
Need info about any TON blockchain address? Try @apitonBot.
It’s a quick and easy way to get details about TON domains, Telegram numbers, and usernames.
Unlike other TON explorers, it instantly shows the status and price of an entity — whether
it’s available for registration or on sale.
Even if an NFT is at auction, you’ll get the owner’s address — all in one request.
Moreover, try to write someone
in chat and se…
Showing the 8 most recent of 8 posts we hold for @apiton. 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@apiton 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@anime named in 1 post, 10 August 2026 – 10 August 2026
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 30 August 2026 — this
entry's latest reading, not the date you are reading this.
“apiTON — explore blockchain” (@apiton), 81 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/apiton.
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.