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 11 August 2026 and assigned it the closest of 31 fixed categories, at 53% 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 (6 of the pairs behind the counts below)
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. 1 of the 2 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 6 comparable posts for this entry, running 1 August 2026 to 7 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).
Across the whole group of 2, the earliest publisher we hold is @Atlantis_Web3 — 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.
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.
3 measurements spanning 3 days, net -5. 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 2,498–2,505 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Aug 2026, 03:03
2,499
-5
7 Aug 2026, 22:51
2,504
no change
7 Aug 2026, 17:18
2,504
first reading
Engagement
12 posts held, back to 1 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
17.5%
avg views ÷ 2,499 subscribers
Avg views / post
437
6 posts measured
Reaction rate
3.47%
reactions ÷ views · ER floor
Posts in window
12
of 12 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
12 (1 August 2026 – 7 August 2026)
Views total
2,621
Reactions total
91
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 17:18 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.
What this channel posts
Video runtime
15s
Average length
3s
Measured directly from 5 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
91 reactions across 6 posts, in 10 distinct kinds. The most used accounts for 40.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
37
40.7%
👏
23
25.3%
🥰
11
12.1%
⚡
6
6.59%
🏆
4
4.40%
🙏
4
4.40%
🤩
3
3.30%
🍾
1
1.10%
👌
1
1.10%
😍
1
1.10%
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 6 of the 12 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 91reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 1 August 2026 to 7 August 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.
📣 Notice to Seed Contributors: Join the .atc Top-Level Domain (gTLD) Project as Co-Founders — Seed Funding Initiative Now Open 🇺🇸💰👏🚀
1. Seed Contributor Funding Opportunity 🎯
The .atc Top-Level Domain (gTLD) Project Community Funding Initiative is now open for all seed contributors.
1) Funding Target: US$1,000,000.00
2) Minimum Contribution: US$1,000 (1,000 USDT, 0.0156 BTC, 1.7036 BNB, or 13.6986 SOL) per…
📢 Updates on Certain Exchange Functions 🇺🇸🔐🚀
🔗 URL: https://AtlantisPro.io
✅ As of today, Atlantis Exchange Pro's deposit functionality is fully operational for both native coins and tokens across the following 8 networks:
1️⃣ Arbitrum
2️⃣ AtlantisChain
3️⃣ Base
4️⃣ BNB Smart Chain (BSC)
5️⃣ Ethereum
6️⃣ Polygon
7️⃣ Solana
8️⃣ TRON
👉 Upgrades for the remaining supported blo…
#Market is changing fast...
#Opportunities are always available somewhere.
If you find and grab a great #opportunity, you #win big!
👇👇👇👇👇👇
📣 Presale + 20% Airdrop: Bitcoin Pizza (PZA) on the World’s #1 FASTEST and MOST Secure Blockchain 🇺🇸🌎🔥🚀
This is a unique memecoin with 100x potential upon listing on exchanges.
On May 22, 2010, Laszlo Hanyecz spent 10,000 Bitcoin (BTC), worth $30, on 2 Papa John's …
📣 Market Update: APEC/USDA Pair Is Live 🔥🚀
💥 Trading URL: https://atlantispro.io/spot/APEC_USDA
💥 Starting Price: 0.000010 USDA
💥 Current Price: 0.008999 USDA
💥 Notes: The listed APEC Coin (APEC) is available on two blockchains:
1⃣ AtlantisChain – Contract: ACj2r8Kk1hj8sLXtYw15TBCFCEQfGHuPKo5nXCFgz4Wj
2️⃣ Ethereum – Contract: 0xa10db72734e4123ee56b8d63b72c0ffade37e680
👉 For more information about APEC Coin, vi…
📣 Important Updates on Atlantis Exchange Pro 🇺🇸🌎🔥🚀
As of August 2, 2026, Atlantis Exchange Pro has successfully completed the Solana blockchain upgrade.
1️⃣ SOL and Solana-based tokens are now available for users to deposit and trade.
2️⃣ Other upgrades, including withdrawals and KYC, are currently underway and will be announced as soon as they become available.
👷♂️ In addition to the deposit functions of the …
📣 Chicago News Journal — Web3 Breaking News: AtlantisChain Rapidly Surpassed 1,100,000,000 Blocks Within 410 Days of Operation and Firmly Holds the World’s #1 Fastest Position in Block Height, Block Time, Finality, and TPS 🇺🇸🌎🔥🚀
💥 Date: July 31, 2026
💥 Summary:
At 10:16 AM on July 30, 2026, Pacific Time, the block height of AtlantisChain — the world’s ONLY ultra-super-fast Layer-0 public blockchain…
❤14👏4⚡1🏆1😍1
Showing the 12 most recent of 12 posts we hold for @Atlantis_Web3. 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 — 813,934 of 1,160,990entries 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 11 August 2026 — this
entry's latest reading, not the date you are reading this.
“AtlantisChain - Official Channel 🌎⚡️🚀” (@Atlantis_Web3), 2,499 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Atlantis_Web3.
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.
