Channel
@toncoin_monster
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001681889469 |
|---|---|
| Type | Channel |
| Username | @toncoin_monster |
| Created | 30 March 2022 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/toncoin_monster |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 17:31 | 7 | no change |
| 7 Aug 2026, 06:24 | 7 | first reading |
10 posts held, back to 30 March 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 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 10 posts for this entry, the most recent from 8 June 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
We launched the functionality of auctions! Now Toncoin Monster Bot allows you to create another type of bot: auction bots. In a few clicks you can create your own bot for auctions in our constructor and start earning TONs. We ourselves and a couple of our customers have already tested it. Everything worked perfectly. The current version is primarily designed for selling NFTs, but you can also auction anything you …
Friends, @toncoin_monster_bot now has a "Pricing" section. These are the prices for using our bot. It works on the freemium model. That is, the start is free, and we only take a commission on the turnover, when you have already started earning with our products. We finally finished our payment system. Huge work, as a result of which we actually repeated the core of Cryptobot. Now the development will go much faster…
May updates We’re speeding up our development. We have two important updates: 1. From now on your users don’t need to go to @tonometerbot to verify their wallet. Everything can be done inside your pre-sale bot in simplified interface and can be run by only one button. It works perfectly everywhere except TonKeeper on Android. By the way, recommend your customers installing TON HUB. This wallet is much more stable.…
We’ve Added Mail-Lists Functionality! Dear friends, one more important update. Since now there is an option of mailing out users in your pre-sale bots. Not simple mailing lists but with an option of segmentation by the size of users’ wallets. Setting and mailing out is embodied through @tonometerbot interface. You can find more details here. It’s implemented as a unified centre of mailing lists for all your bots …
Dear friends! Now we see that quite a few projects have already started selling their NFTs through our pre-sales bot. Please share your experiences. What did you like/dislike? What is missing? What would you add? In the nearest update: — Referral system for your pre-sales (automatically sets and calculates commissions of your partners). — Payment system. We don't charge a fee for our services yet. The payment sy…
Why minting without pre-sales poses a great risk? One can often hear that NFT projects don’t want to conduct pre-sales, since in their view it is more correct to immediately start selling with minting. But they’re missing one pivotal point. A project is being prepared for 2-3 months (marketing, advertising, design, preparation take time) in order to try out for minting only once. This increases the risks greatly.…
For what do we need pre-sales when marketplaces and mint do already exist? We often hear this question, that is why we decided to give a centralised answer. Let’s take as a reference point good old stock market. It already exists from the times of Dutch East India Company. It’s by the way 17th century. An incredible multitude of the ways of storage, verification and trading of securities were created during next 40…
It’ not only pre-sales bot functionality We’d like to pay your attention to the fact that we present it’s not simply a bot for collecting money for NFTs. It is a full-fledged platform. 1. You can create different stages of your sales. With different price and amount of NFTs. 2. Verification of your buyers through Tonometer let you avoid a lot of troubles. For example, the users can easily move in Tonometer from …
Dear friends, we have finally launched our own platform for all NFTs, Telegram channels and bots creators based on TON. It’s called Toncoin Monster. The logic of the name is simple: we create a platform and services on its base that are working on TON blockchain and using Toncoin for payments. And “Monster” because this bot will become the only place for entry and administration for dozens of our services under de…
Channel created
Showing the 10 most recent of 10 posts we hold for @toncoin_monster. 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 — 1,021,300 of 1,481,217entries 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.
Named by 1 registered channel — 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Toncoin Monster” (@toncoin_monster), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/toncoin_monster.
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.