Channel
@Mercury_Tools_Announcements
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,193subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001727251240 |
|---|---|
| Type | Channel |
| Username | @Mercury_Tools_Announcements |
| Created | Between 1 December 2021 and 19 April 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/Mercury_Tools_Announcements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 11:53 | 1,193 | -1 |
| 14 Aug 2026, 09:58 | 1,194 | -2 |
| 7 Aug 2026, 19:47 | 1,196 | -1 |
| 7 Aug 2026, 05:16 | 1,197 | no change |
| 7 Aug 2026, 05:05 | 1,197 | first reading |
20 posts held, back to 19 April 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 20 posts for this entry, the most recent from 13 July 2022. An engagement rate over an empty window would be a number about nothing.
Mercury Tools Announcements pinned «Hello dear Mercury holders. The past months have been very challenging for us. We made huge advertising payments out of our own pockets. We even published led billboard advertisements on the biggest streets of Istanbul. But the timing was very bad. Despite…»
Hello dear Mercury holders. The past months have been very challenging for us. We made huge advertising payments out of our own pockets. We even published led billboard advertisements on the biggest streets of Istanbul. But the timing was very bad. Despite everything, we gave very good profit opportunities and, unlike other projects, we survived for months. Even when many people were selling due to market panic, we s…
Price protection is still continue. Stake program will start in few days.
Burns will continue this week to protect the price. Market is bleeding but Mercury stands! Just burnt some tokens again and caused to 20% pump. We will see more this week. Don't forget to tell this to your friends and family! Marketing is not good option while market is bleeding and it can cause too much budget without return. Because people are in loss now. So we need to touch people's heart 🙂 There will be few good…
Video, posted without a caption
Video, posted without a caption
Video, posted without a caption
🚨IMPORTANT ANNOUNCEMENT Trading competition with led billboard commercials is coming up! By buying or selling mercury, you will get a chance to win 1,000$ at between of Thursday 12:00 and Saturday 12:00 (afternoon). The only rule is; buy amount must be higher than sell amount until the end of the competition. Winner will be announced at Sunday. Next good news is; taxes are lowered to 3% for buy, 6% for sell! P.S:…
🚨 TAX: IMPORTANT ANNOUNCEMENT - We currently have given up on our personal tax revenues for a while and updated the buy tax to 8% and sell tax to 10%. Now, all the tax goes to the marketing wallet so that we can have boost marketing in the following days.
🚨 IMPORTANT ANNOUNCEMENT We increased the deflation of the token by using a new burn mechanism and liquidity contribution. Price will increase more than old. Taxes will stay same as 2% for buys, 4% for sells. How new mechanism works; Half of the taxes going to the liquidity pool as token+bnb then we burn the tokens from the liquidity pool and bnb stays. Price calculations are based on token/bnb=price formula. While…
Let's do some good comments to our CMC page before our trending plan! https://coinmarketcap.com/currencies/mercury-tools/
We are planing to be trended at CMC or DexTools soon.
Showing the 12 most recent of 20 posts we hold for @Mercury_Tools_Announcements. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“Mercury Tools Announcements” (@Mercury_Tools_Announcements), 1,193 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/Mercury_Tools_Announcements.
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.