Im closing this till sushiswap got volume

Channel
Sushi Robinhood
@sushilaunchpad
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004402358168 |
|---|---|
| Type | Channel |
| Username | @sushilaunchpad |
| Created | Between 1 June 2026 and 6 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/sushilaunchpad |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 05:47 | 2 | no change |
| 14 Aug 2026, 20:45 | 2 | first reading |
Engagement
20 posts held, back to 6 August 2026 — 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.
- ERR · 30 days
- 160.0%
- avg views ÷ 2 subscribers
- Avg views / post
- 3.2
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (6 August 2026 – 6 August 2026) |
| Views total | 64 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 20:45 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
Name: Unagi Symbol: EEL Dev Buy: 0.0005 ETH Dev Hold: 0.00% Creator: 0x40cF06ca8B5a445258D1db7bb79584f829FF9C15 Deploy Count: 4 Token Address: 0x84f73cBe3d3e80Bc44aF8b0067d4f678A2895138 Chart: DexScreener
Name: HAMACHI Symbol: HAMACHI Dev Buy: 0.0005 ETH Dev Hold: 0.00% Creator: 0x8189Ddb8A3C365Fab5eD4596c079F32cfa990d36 Deploy Count: 2 Token Address: 0x894e3324E9AB95aF0Ae1796af5a25a3Cf6BaFE7F Chart: DexScreener
Name: FlamingoBro Symbol: FLAMINGOBRO Dev Buy: 0.131387116189349431 ETH Dev Hold: 4.79% Creator: 0x22063D2491Ce09e44aA1aB21275f1944aD15075F Deploy Count: 1 Token Address: 0x29B0057555D40f6189C05ca66C5D3dBfb841A4f7 Chart: DexScreener
Name: SUSHIGUY Symbol: SGY Dev Buy: 0.005735484647573977 ETH Dev Hold: 0.20% Creator: 0x42f229D53Bb6727F57BaAdBfAb9323D809CAb722 Deploy Count: 1 Token Address: 0x02124473643f017b947B94959d5d64E893059330 Chart: DexScreener
Name: wars Symbol: WARS Dev Buy: 0.026655238106853726 ETH Dev Hold: 1.00% Creator: 0x93f7c76D5f90a1a9336E5f8743B1eA25A6C9Ccd7 Deploy Count: 1 Token Address: 0x08A0c42D56183b39D59cAd3F7B4CFD2EC7C0C252 Chart: DexScreener
Name: Robinhood Connect Symbol: CONNECT Dev Buy: 0.0005 ETH Dev Hold: 0.00% Creator: 0xd2279b05C7a47D85E6B67D15d624332057F38FA2 Deploy Count: 4 Token Address: 0x332c5dec45de1d530276781fE147d8237E759386 Chart: DexScreener
Name: SUSHI HOOD Symbol: SUSHIOOD Dev Buy: 0.005731047621370745 ETH Dev Hold: 0.20% Creator: 0x6b12E36F4DC9aC2DE11e024d95dDB625cc644b47 Deploy Count: 1 Token Address: 0xa077Ea184d4976D4B8713a464e36eD3Fa817b563 Chart: DexScreener
Name: SUSHIFRONG Symbol: SFR Dev Buy: 0.005731047621370745 ETH Dev Hold: 0.20% Creator: 0xA11b9c5d5735f6F392cDe5D9788586975d630A21 Deploy Count: 1 Token Address: 0x3B535C1b2f7825F5c1FD56B6DbBBa0Ee60a1602B Chart: DexScreener
Name: vladwifhat Symbol: HAT Dev Buy: 0.0005 ETH Dev Hold: 0.00% Creator: 0x40cF06ca8B5a445258D1db7bb79584f829FF9C15 Deploy Count: 3 Token Address: 0x97676cBC21E40bcfB9ba296191B1696C71A30653 Chart: DexScreener
Name: Saturn day Symbol: SATURN Dev Buy: 0.0005 ETH Dev Hold: 0.00% Creator: 0xd2279b05C7a47D85E6B67D15d624332057F38FA2 Deploy Count: 3 Token Address: 0x7308BD0bd9D27254A6c144905e47e81c01527Fa3 Chart: DexScreener
Name: HOOD Summit Symbol: SUMMIT Dev Buy: 0.0005 ETH Dev Hold: 0.00% Creator: 0x8189Ddb8A3C365Fab5eD4596c079F32cfa990d36 Deploy Count: 1 Token Address: 0xFa25652340BdCf272C045eff45E43fa3b62F30e1 Chart: DexScreener
Showing the 12 most recent of 20 posts we hold for @sushilaunchpad. 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
Citation-graph rank — 1,412,968 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.
Mentions
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.
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Sushi Robinhood” (@sushilaunchpad), 2 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/sushilaunchpad.
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.