Live stream finished (27 minutes)

Channel
inch
@inch_ton
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
491subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002103943493 |
|---|---|
| Type | Channel |
| Username | @inch_ton |
| Created | 26 April 2024 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/inch_ton |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 23:51 | 491 | no change |
| 8 Aug 2026, 09:30 | 491 | first reading |
Engagement
16 posts held, back to 26 April 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 pageof 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 16 posts for this entry, the most recent from 15 October 2024. An engagement rate over an empty window would be a number about nothing.
Reaction mix
209 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 31.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 65 | 31.1% | |
| custom 5339123272141263609 | 44 | 21.1% | |
| ❤ | 32 | 15.3% | |
| 👍 | 26 | 12.4% | |
| 🤯 | 12 | 5.74% | |
| custom 5323579660942985502 | 9 | 4.31% | |
| ⚡ | 9 | 4.31% | |
| 🍌 | 5 | 2.39% | |
| 🫡 | 4 | 1.91% | |
| 🍾 | 2 | 0.957% | |
| 🤝 | 1 | 0.478% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 14 of the 16 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 209reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 26 April 2024 to 15 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
- Stars received
- 50
- across the posts below
- Posts paid on
- 1
- of 14 we hold a reading for · 7%
- Most on one post
- 50
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @inch_ton. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 16 most recent posts we hold for this entry, published 26 April 2024 to 15 October 2024. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
📣 Application update We have done a great job and hasten to present you the next update of our application. [version 1.2.1] This update includes the following innovations: — Daily rewards for entering the application have been added. The reward increases every day! — Leaderboard has been added, which contains the «Top 100» of tINCH points holders, as well as your personal rating among all users. — The profile ha…
🔥6❤3👍2🤯1
🗣 Open AMA session On October 16, an open AMA session of two crypto projects - inch and SHIBA a channel specializing in news from the world of cryptocurrencies). At this meeting, you will have an honest and frank conversation about the plans, goals and prospects of the inch project 🤑 Some interesting issues will also be discussed: - Why was the choice made towards Open Source? - What partnerships should we expect i…
❤4🔥2
🖥 Meet the «Tasks» We are pleased to announce the release of an update for the inch app. Now all users of the application have access to tasks #️⃣, for which a corresponding reward will be awarded. The first tasks are already available in the app. 🤝 For cooperation and placement of your projects in the «Tasks» section, you can contact project support: @inch_support. Also, in the new version, bugs have been fixed a…
👍5🔥3🍾2
🖥 Launching a Web-application We are in a hurry to introduce inch app - a new page in the history of our project 🥳 The basic functionality is already available, including "mining" with a system of improvements and a referral system. The web application is a solid foundation on which new mechanics and events will gradually be built 📣 We remind you that anyone can participate in the development of the project. We wo…
🔥8⚡2👍2
🤖 We are open to the community Recently, our project has been hosted on the well-known GitHub site in the «organization» format. This step erases the line of distrust between the project team and the community 🗣 Anyone can open and check the source code of any of our products, thereby making sure that it is «honest». It is impossible not to mention that the placement of our code base on GitHub gives our entire com…
❤7🔥6👍4⚡1
🖥 Preparing for launch There are only a few days left before the launch of our application (WebApp) on the Telegram platform. On 29.08 we will launch a closed beta testing with the participation of a team of testers formed from members of our community 🤝 🏳️ Submit a request to the beta testing program At the end of the above stage, we will need several days to find errors and fix them 🚫 We are sure that this work…
🔥9❤6🫡4⚡1
🏳️ Cooperation with BingX 💰 We are pleased to announce the beginning of inch cooperation with the BingX cryptocurrency exchange. Together with the BingX team, we are launching a special affiliate program for our community. 🕯 Right now you can register on BingX and start trading by choosing a convenient cryptocurrency pair. The exchange also makes it possible to carry out fast and secure P2P transactions. ⚠️ Parti…
🤯11👍5⚡3
🏳️ Pack of branded Emojis Each community member who owns Telegram Premium can support our project and put any emoji from the pack in the status. Emoji: 🏳️🏳️🪙 ➡️ Add emoji pack Many thanks to @kotletovv for creating this amazing pack. CHANNEL | CHAT | BOT
🔥10❤3⚡2
We share with you the current statistics of the project 🔄 Since the launch of the project, we have gained some fame in narrow circles of users. At the moment, 620 users are subscribed to the project channel. During its entire existence, Independent Chain Bot has been launched 2,246 times. At the same time, only 16.3% of bot users take part in the «Mining» program. At the same time, 824,225 $tINCH have already been m…
🔥12👍4custom 53391232721412636094❤1
We are glad to announce the collaboration Independent Chain with the educational project RevolutiON 🙏 Based on the latest trends in the internet, it can be concluded that many users have become interested in projects that appear in the world of cryptocurrency. Many do not have sufficient knowledge and skills to assess all the prospects and risks. The RevolutiON project offers users in an accessible and desirable fo…
custom 533912327214126360911❤8🔥4👍1🤝1custom 53235796609429855021
Each participant of the Independent Chain project can participate in the "mining" of $tINCH points using the Telegram bot of the project. Points are the numerical equivalent of the $INCH token and can be further converted. At the moment, the token is minted on the TON Minter platform and has a "total offer" of 10,000,000 $INCH. The ownership of the token has already been revoked. This condition guarantees a fixed ca…
custom 53235796609429855028🔥2custom 53391232721412636092
Showing the 12 most recent of 16 posts we hold for @inch_ton. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank
Citation-graph rank — 172,446 of 1,176,251entries 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 2 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.
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
- 6
- 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
- 6
- vacant every time we have ever looked
@inch_ton named 6 handles 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.
named in 6 posts, 9 August 2026 – 9 August 2026
named in 5 posts, 9 August 2026 – 9 August 2026
named in 5 posts, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“inch” (@inch_ton), 491 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/inch_ton.
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.