Channel
@StandardRockets
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
2,760subscribers
-11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001972618845 |
|---|---|
| Type | Channel |
| Username | @StandardRockets |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/StandardRockets |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @StandardRockets/866 · this entry8 Aug 2024, 16:00 UTC | @DoomMoverz/6078 Aug 2024, 16:00 UTC | 1.00 | under a minute |
| @DoomMoverz/6128 Aug 2024, 17:03 UTC | @StandardRockets/871 · this entry8 Aug 2024, 17:03 UTC | 1.00 | under a minute |
| @DoomMoverz/6138 Aug 2024, 17:05 UTC | @StandardRockets/872 · this entry8 Aug 2024, 17:05 UTC | 1.00 | under a minute |
| @DoomMoverz/62617 Aug 2024, 16:59 UTC | @StandardRockets/886 · this entry17 Aug 2024, 16:59 UTC | 1.00 | under a minute |
| @DoomMoverz/62928 Aug 2024, 16:26 UTC | @StandardRockets/889 · this entry29 Aug 2024, 09:41 UTC | 1.00 | 17 hours |
| @DoomMoverz/61714 Aug 2024, 17:52 UTC | @StandardRockets/877 · this entry14 Aug 2024, 17:54 UTC | 0.99 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @DoomMoverz | 8 (8/8 hand-verifiable sample passed) | 0.98 | under a minute | this entry (6–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 2 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 8 August 2024 to 29 August 2024. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @StandardRockets — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 00:11 | 2,760 | -11 |
| 7 Aug 2026, 15:58 | 2,771 | no change |
| 7 Aug 2026, 11:17 | 2,771 | first reading |
20 posts held, back to 8 August 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 2 pagesof 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 29 August 2024. An engagement rate over an empty window would be a number about nothing.
🚀 WE ARE BACK AND READY TO PRINT 🚀 Pardon the delay, we have been in the lab brewing something juicy. Over the next few days we will be dropping some absolute alpha. Turn on notifications so you don't miss our calls Get ready for one of the biggest moonshots you've ever seen. 💰
The token we are pumping today is:🐋 RMT ($RMT) 🚀 CONTRACT: 0xAAbB26E8C7b5CcaCca0db5b2835602B3a4a9Cf (Tap on the CA to copy it) UNISWAP: https://app.uniswap.org/swap?outputCurrency= 🦄 Uniswap link 🦄 GOOD LUCK! BE QUICK AS THIS WILL FLY. 🔥100X+ COMING IN HOT🔥
10 MINUTES REMAINING NEXT MESSAGE IS TOKEN WITH ALL RELEVANT INFO! THIS THINGS ABOUT TO FLY!!!!!
30 minutes remaining 🕰 The time is almost here. We recommend you to have Uniswap.org open on one tab, and telegram open on the other. Copy & paste the contract address we send into Uniswap, turn slippage up and get your buy in as fast quick as possible. We will give sell signals, but of course you are free to take profits whenever. Inquires: @CryptoBagGod
1 HOUR REMAINING 🕰 ⚡️ETHRIUM ⚙️ Taxes: 0/0 🧼 Slippage: 30+% for buying 🪙 ETH: .3-5+ recommended ⛽️ Gas: 30+ 📝Sell tips: we always recommend our members to sell in multiple transactions. For example, if you buy 1000 tokens, you will sell in 5 transactions of 200 tokens every 10-15 minutes.
2 hours remaining 🚥 We are getting close to our signal. The most important and useful tip we can give you is USE HIGH SLIPPAGE! 20-30%. Prices move so fast, and in the gist of a 100x+ a 20-30% slippage is nothing. Taxes are 0/0 for this token. Guys, we are presenting an extremely talented team that we believe will fly to $100m within the first few days. We are extremely lucky to be getting in firsthand and before a…
11 hours remaining 🕰 YOU WILL NOT WANT TO MISS THIS ONE 🚀🚀🚀🚀🚀🚀 We have a very juicy play lined up with some of the biggest KOL/AMA groups in the game. We are expecting a solid 80-100x return with at least $10+m in volume. We have a huge marketing push set to begin shortly after we announce it here. We want as many of you to get in before we start, as this will bring the majority of the volume. If this is your fir…
Live stream scheduled for Aug 17, 2024 at 17:00
🚀 22 HOURS TILL PUMP 🚀 Countdown live! Check top of channel for live countdown! Don’t forget to set an alarm
📈 BIGGEST COLLAB PUMP INCOMING 📈 - Upcoming Signal - August 17th @ 17:00 UTC - ETH/Uniswap We have a arguably the biggest collab play lined up on this date & time. We have prepped one of the craziest projects coming into this space, we are expecting this one to explode. Right now is the best time to take advantage of Ethereum/base plays as gas fees are the lowest they’ve been in a while. You will need native Ethe…
Signal Review/Summary: Signal Stats: • 7464.37% return (74X) • 4.2M + under 6 hours • #4 on trending • Successful marketing campaign launched post call. • Call pumped for 12+ hours straight with only two main pull back. This shows how important it is to take initials. To those who made a killing yesterday, congrats. We had an insane pump last week. One of the best we've seen for awhile. Crazy part is, I checked bac…
We are prepping 4 KOLs, a slot on @trending secured in about 24 minutes, and a call coming from 3 caller groups for this token! GET READY TO FLY 🔥
Showing the 12 most recent of 20 posts we hold for @StandardRockets. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“ETH WHALES 🐋” (@StandardRockets), 2,760 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/StandardRockets.
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.