Telegram RegisterThe public register of Telegram

Channel

404 zone

@metaverse404ch

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

9,999subscribers

-46 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-1002276376883
TypeChannel
Username@metaverse404ch
DescriptionMetaverse: https://404universe.com For desktop and laptop 💻 For partnerships: @pokemonowner
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/metaverse404ch

Topic

Other / unclassifiable — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 48% 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.

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 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.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@metaverse404ch/325 · this entry3 Jul 2025, 22:30 UTC@gigachadhub/2543 Jul 2025, 22:32 UTC1.0072 seconds
@metaverse404ch/327 · this entry28 Jul 2025, 08:23 UTC@gigachadhub/26028 Jul 2025, 08:24 UTC1.0072 seconds
@gigachadhub/27026 Nov 2025, 22:33 UTC@metaverse404ch/333 · this entry26 Nov 2025, 22:34 UTC1.0072 seconds
@gigachadhub/27227 Nov 2025, 22:01 UTC@metaverse404ch/335 · this entry27 Nov 2025, 22:01 UTC1.00under a minute
@metaverse404ch/339 · this entry4 Jan 2026, 14:32 UTC@gigachadhub/2764 Jan 2026, 14:39 UTC1.007 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@gigachadhub6 (6/6 hand-verifiable sample passed)1.0072 secondsthis entry (42)

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 10 comparable posts for this entry, running 28 June 2025 to 18 January 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).

Across the whole group of 2, the earliest publisher we hold is @metaverse404ch — 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 8 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.

Also posting the same content

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.

Growth

9,99910,04510,0227 August 2026 — 10,045 subscribers8 August 2026 — 10,039 subscribers9 August 2026 — 10,033 subscribers10 August 2026 — 10,014 subscribers11 August 2026 — 9,999 subscribers7 August 202611 August 2026
5 measurements spanning 4 days, net -46. 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 9,992–10,052 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 13:529,999-15
10 Aug 2026, 14:4110,014-19
9 Aug 2026, 12:3310,033-6
8 Aug 2026, 15:1310,039-6
7 Aug 2026, 15:1510,045first reading

Engagement

20 posts held, back to 13 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 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 18 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
21
Videos
4
Links
24

Lifetime counters from Telegram’s own channel header, read 12 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.

Video runtime
6m 08s
Average length
2m 03s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

41 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 39.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1639.0%
👍1434.1%
😁717.1%
❤‍🔥24.88%
🔥24.88%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 11 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 41reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 June 2025 to 18 January 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

18 Jan 2026, 13:18 UTC≈1,380 views1 reactionsread 12 August 2026
Forwarded from @buinkers

🚀 Buinkers 💩 💩 Buinkers is a community-driven P2E parody project building toward the launch of its core asset — Holy Shitcoin. The project blends humor, fair access, and community participation to shape token distribution at TGE, with no gambling mechanics involved. At its core, Buinkers is designed around engagement-based allocation, where community activity and participation help determine Holy Shitcoin distributi

1

7 Jan 2026, 06:16 UTC≈1,430 viewsread 12 August 2026
Forwarded from @buinkersPhoto

Contest! ⭐️ Everyone who purchases 1000+ batteries in @buinkersbot are eligable for a chance to receive one of the prizes above. Wheel of names will decide. Drop your number of spins here 👇 P.s. Cheating not allowed, we see all the transactions and balances of players, photoshop won’t work here, so don’t even try. 7 days, ending 2026.01.14! @buinkers

4 Jan 2026, 14:32 UTC≈1,410 viewsread 12 August 2026
Video

Buinkers is the holy Parody farming game: Spin the wheel to charge your poor machine, collect shitcoins, and boost your income with bananas! It’s chaotic, fun, and surprisingly addictive and yes, it’s free to play via @buinkersbot If you’re into meme mechanics and play‑to‑earn vibes, this one’s for you. Want more? Limited equity spots available at getgems.io/buinkers Channel: @buinkers Chat: @buinkerschat Game: @

27 Nov 2025, 22:01 UTC≈1,820 views1 reactionsread 12 August 2026

I just found a very unique handle and decided to start my call channel. This is it: @symphonyclub Join and let it grow smoothly! Happy thanksgiving! Appreciate you guys ;)

❤‍🔥1

26 Nov 2025, 22:34 UTC≈1,720 views1 reactionsread 12 August 2026
Video

Let me explain how the revenue model for our private buyers works. As example we raise $50k in private sale and your investment is $5k( just to catch the right numbers easily ) - meaning your share is 1.5%( private buyers shares 15% of the whole thing) of the total metaverse revenue including all ingame purchases, NFT land and avatar sales, etc. So all that means - 1M of metaverse volume brings you $15k just for yo

❤‍🔥1

21 Nov 2025, 10:17 UTCviews —

404 zone pinned «Hey guys! I am fully back and active to skyrocket our metaverse game! What is coming next: We are rebranding and gonna have an absolute new name and structure in the game! We gonna be actively building the community for the next couple of months and each…»

21 Nov 2025, 10:16 UTC≈1,440 views1 reactionsread 12 August 2026
Forwarded from @metav404

Hey guys! I am fully back and active to skyrocket our metaverse game! What is coming next: We are rebranding and gonna have an absolute new name and structure in the game! We gonna be actively building the community for the next couple of months and each referral receives special prizes during the community build up. I appreciate all you for the patience! Now we gonna prove that our metaverse is the next gem in t

🔥1

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

Forward network

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.

Mentions

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.

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

“404 zone” (@metaverse404ch), 9,999 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/metaverse404ch.

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.