Telegram RegisterThe public register of Telegram
Telegram profile photo for Meme to the Moon

Channel

Meme to the Moon

@MemeExplosiontu

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Posts recorded as deleted · Cite this entry

3,420subscribers

-882 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002008359812
TypeChannel
Username@MemeExplosiontu
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/MemeExplosiontu

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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 the other topics.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 10 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@MemeCoinIntelligence/202716 Aug 2026, 20:20 UTC@MemeExplosiontu/33022 · this entry6 Aug 2026, 20:20 UTC1.00under a minute
@MemeCoinIntelligence/202766 Aug 2026, 21:38 UTC@MemeExplosiontu/33027 · this entry6 Aug 2026, 21:38 UTC1.00under a minute
@MemeCoinIntelligence/202867 Aug 2026, 11:32 UTC@MemeExplosiontu/33037 · this entry7 Aug 2026, 11:33 UTC1.00under a minute
@MemeCoinIntelligence/202947 Aug 2026, 18:06 UTC@MemeExplosiontu/33045 · this entry7 Aug 2026, 18:06 UTC1.00under a minute
@MemeCoinIntelligence/202998 Aug 2026, 01:25 UTC@MemeExplosiontu/33050 · this entry8 Aug 2026, 01:25 UTC1.00under a minute
@MemeCoinIntelligence/203048 Aug 2026, 06:49 UTC@MemeExplosiontu/33055 · this entry8 Aug 2026, 06:49 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@MemeCoinIntelligence7 (6/7 hand-verifiable sample passed)1.00under a minute@MemeCoinIntelligence (7–0)
@CaptainWolfema7 (6/7 hand-verifiable sample passed)1.00under a minute@CaptainWolfema (5–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. 12 of the 12 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 7 comparable posts for this entry, running 6 August 2026 to 8 August 2026. 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 10 channels, the one whose matching posts we hold earliest is @alphagmescallers111. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 10 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

3,4204,3023,8617 August 2026 — 4,302 subscribers7 August 2026 — 4,302 subscribers8 August 2026 — 4,284 subscribers11 August 2026 — 4,232 subscribers15 August 2026 — 4,188 subscribers18 August 2026 — 4,118 subscribers20 August 2026 — 4,107 subscribers24 August 2026 — 4,068 subscribers26 August 2026 — 4,028 subscribers29 August 2026 — 4,009 subscribers1 September 2026 — 3,970 subscribers5 September 2026 — 3,910 subscribers10 September 2026 — 3,828 subscribers14 September 2026 — 3,738 subscribers18 September 2026 — 3,694 subscribers27 September 2026 — 3,609 subscribers5 October 2026 — 3,582 subscribers12 October 2026 — 3,520 subscribers15 October 2026 — 3,500 subscribers18 October 2026 — 3,498 subscribers21 October 2026 — 3,488 subscribers24 October 2026 — 3,484 subscribers27 October 2026 — 3,458 subscribers30 October 2026 — 3,445 subscribers2 November 2026 — 3,436 subscribers5 November 2026 — 3,431 subscribers8 November 2026 — 3,420 subscribers7 August 20268 November 2026
27 measurements spanning 93 days, net -882. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,288–4,434 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
8 Nov 2026, 06:573,420-11
5 Nov 2026, 09:493,431-5
2 Nov 2026, 03:283,436-9
30 Oct 2026, 03:063,445-13
27 Oct 2026, 08:003,458-26
24 Oct 2026, 00:583,484-4
21 Oct 2026, 04:213,488-10
18 Oct 2026, 08:083,498-2
15 Oct 2026, 12:313,500-20
12 Oct 2026, 14:273,520-62
5 Oct 2026, 11:403,582-27
27 Sept 2026, 08:383,609-85
18 Sept 2026, 02:173,694-44
14 Sept 2026, 06:203,738-90
10 Sept 2026, 18:213,828-82
5 Sept 2026, 21:573,910-60
1 Sept 2026, 21:343,970-39
29 Aug 2026, 16:264,009-19
26 Aug 2026, 22:234,028-40
24 Aug 2026, 09:054,068first reading

Engagement

32 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 5 pages of 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 32 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 06:53 UTC15 viewsread 8 August 2026
Photo

$Doom did 100x at ath followed by retractions now recovering

8 Aug 2026, 06:49 UTC14 viewsread 8 August 2026
Photo

$Racoonzilla on RB recently launched chart looking good around 70k currently BNB one is 1M+ dope graphics & decent volume drop by

8 Aug 2026, 01:25 UTC21 viewsread 8 August 2026
Photo

BSC BRCG just launched. In early 2013, an artist named Marcus created Bitcoin Roller Coaster Guy after seeing people describe Bitcoin’s price movements as a roller coaster ride. He shared the animated GIF on BrainlessTales, Bitcointalk, and Reddit, where it began spreading through the early Bitcoin community. It became the very first crypto meme to exist and predates $DOGE, which launched in December 2013. $BRCG …

7 Aug 2026, 19:28 UTC27 viewsread 8 August 2026
Photo

Dream 3x 500k mc at ATH now around 300k 🔥 3UGJHrLqzbX4g7GdAWAn5XkhVApT4WHxAewntuWJpump

7 Aug 2026, 18:06 UTC29 viewsread 8 August 2026
Photo

Robinhood $HMM good launch watch entries new team sent by a marketer! Thinking my way to billions… $HMM… Thinking Cat 0x7FE995a80075dF3Dc8Ae11A9b82c7FE4202CD87f

Showing the 12 most recent of 32 posts we hold for @MemeExplosiontu. 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.

Posts recorded as deleted after publishing

We recorded 2 posts on @MemeExplosiontu as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
7 August 2026
Median time before seen missing
9.5 hours
Seen missing in the last 30 days
0

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 8 November 2026 — this entry's latest reading, not the date you are reading this.

“Meme to the Moon” (@MemeExplosiontu), 3,420 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/MemeExplosiontu.

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.