Channel
@sato_tech
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
39subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002099646168 |
|---|---|
| Type | Channel |
| Username | @sato_tech |
| Description | Our bots: - @ChainScout_bot - @PumpTheFun Support: @satosphere |
| Created | 7 February 2024 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/sato_tech |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 20:01 | 39 | no change |
| 7 Aug 2026, 13:58 | 39 | first reading |
15 posts held, back to 7 February 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 15 posts for this entry, the most recent from 31 October 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
🚨 Exciting Update from SatoTech! 🚨 We’re thrilled to announce the launch of our newest bot, @PumpTheFun_bot As a result, this channel has been rebranded as SatoTech, your central hub for updates on current and upcoming bots. About @PumpTheFun_bot This bot allows you to seamlessly deploy tokens directly on Pump.fun right from both DM and groups! Support Group Need assistance? Join our support community at @PumpTh…
Channel photo updated
Channel name was changed to «SatoTech»
New upgrade has been pushed out, primarily focusing on TON scans. A link to Tonviewer now works, buy button for Stonks has been added, Dextools link is also added and will work once they add support for TON. I have also addressed the issue of the bot going down, the new upgrade should hopefully solve this and make it run smoothly 24/7.
TON chain is now available on Dexscreener, as a result the /ton command is no longer needed. You can now fetch info on TON tokens as you normally would on other chains. NB: Only pools on Dedust are supported for now.
🔗 New update 🔗 - /d command has been removed and been replaced by a 'Detailed' button instead. A 'Basic' button will also display when in detailed view, allowing you to switch back and forth. - Bot now picks up on CAs automatically, simply paste an address and the bot will respond with a basic scan.
🔗 New update 🔗 /ton followed by a contract address will now provide basic info about a token on the ton network.
🔗 New update has been been pushed out 🔗 /holders followed by contract address and chain now gives you the top 10 holders of a token, along with a link to their wallet and how much they are holding. Not available for SOL
🔗 New update has been been pushed out 🔗 /d will now give you a more detailed scan, including: Can Take Back Ownership Blacklist Mint Proxy Contract Hidden Owner Ownership address See https://t.me/chainscoutbots/7 for detailed information. Minor improvements: - Dev wallet added - More chains added - Sniper buttons for bsc and arb
Fake Renounce Owner can still retrieve control of the contract, even after being renounced. Effectively a fake renounce. May not be detected if a proxy is detected. Blacklist: The contract owner may add any address to the blacklist, and the token holder in the blacklist will not be able to trade. If a contract is renounced, the function will most likely be disabled. May not be detected if a proxy is detected. Som…
🔗 New data added to /i and $ command 🔗 - Total holders - Honeypot check - Tax - Twitter - Direct search for token ticker Note: Total holders, honeypot check and tax will only be visible on tokens running on BSC and ETH.
SatoTech pinned «🔗 Available Commands for @ChainScout_bot 🔗 /i and $ This can be used to grab information about a token, simply do /i or $ followed by either contract, name or ticker. Furthermore, you can also specify chain by adding this at the end. /d Will give you…»
Showing the 12 most recent of 15 posts we hold for @sato_tech. 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 — 576,830 of 1,585,381entries 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.
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.
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.
@sato_tech named 3 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.
References a handle that is not a live channel — we have no record it ever was one.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“SatoTech” (@sato_tech), 39 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/sato_tech.
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.