Telegram RegisterThe public register of Telegram

Channel

New Pairs - DEX Screener

@DSNewPairs

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Cite this entry

2,311subscribers

-10 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001621981937
TypeChannel
Username@DSNewPairs
CreatedBetween 1 December 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/DSNewPairs

Topic

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 100% 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)
Posted firstThenOverlapGap
@DSNewPairs/2897083 · this entry18 Feb 2025, 13:47 UTC@DSNewPairsSolana/99615218 Feb 2025, 13:47 UTC1.00under a minute
@DSNewPairs/2897084 · this entry18 Feb 2025, 13:47 UTC@DSNewPairsSolana/99615318 Feb 2025, 13:47 UTC1.00under a minute
@DSNewPairs/2897085 · this entry18 Feb 2025, 13:47 UTC@DSNewPairsSolana/99615418 Feb 2025, 13:47 UTC1.00under a minute
@DSNewPairs/2897087 · this entry18 Feb 2025, 13:47 UTC@DSNewPairsSolana/99615618 Feb 2025, 13:47 UTC1.00under a minute
@DSNewPairs/2897088 · this entry18 Feb 2025, 13:47 UTC@DSNewPairsSolana/99615718 Feb 2025, 13:47 UTC1.00under a minute
@DSNewPairs/2897092 · this entry18 Feb 2025, 13:47 UTC@DSNewPairsSolana/99616018 Feb 2025, 13:47 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@DSNewPairsSolana15 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (150)

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 0 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 20 comparable posts for this entry, running 18 February 2025 to 18 February 2025. 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 @DSNewPairs — 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.

Growth

2,3112,3212,3167 August 2026 — 2,321 subscribers7 August 2026 — 2,321 subscribers7 August 2026 — 2,320 subscribers10 August 2026 — 2,311 subscribers7 August 202610 August 2026
4 measurements spanning 3 days, net -10. 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,310–2,323 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 16:412,311-9
7 Aug 2026, 14:212,320-1
7 Aug 2026, 14:032,321no change
7 Aug 2026, 12:162,321first reading

Engagement

20 posts held, back to 18 February 2025the 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.

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 February 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

19 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 36.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😭736.8%
😢526.3%
👎315.8%
👍210.5%
15.26%
🔥15.26%

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 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 19reactions 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 18 February 2025 to 18 February 2025, 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 Feb 2025, 13:48 UTC≈1,810 views16 reactionsread 7 August 2026

🌱 New Pair on Solana: Jailer Milei - MILEI / SOL 📍 DEX: Solana / Raydium Token address: dEEDMKqBFQToZa7huFcsrW93tMoGtu82s6mLUrtFRVk Price USD: $0.00008521 Price: 0.0000005026 SOL FDV: $85,215 Total liquidity: $169,975 Pooled MILEI: 998,573,362 Pooled SOL: 500.7211 ($84,891) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

😭7😢5👎31

18 Feb 2025, 13:48 UTC≈1,680 views0 reactionsread 7 August 2026

🌱 New Pair on Solana: BAX - BAX / SOL 📍 DEX: Solana / FluxBeam Token address: 78iQ2Rn1SnHFs8zBK8rLLBZ3H1E17vrGHouC1QGYtobS Price USD: $0.0003535 Price: 0.000002084 SOL FDV: $353,191 Total liquidity: $19,374 Pooled BAX: 48,944,751 Pooled SOL: 12.2 ($2,069) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

18 Feb 2025, 13:48 UTC≈1,160 viewsread 7 August 2026

🌱 New Pair on Solana: BlockMind AI - BlockMind / SOL 📍 DEX: Solana / Raydium Token address: CBVRVqcSHVmb9Y4ABvnYDTTYDLJVsRHfBsy7aC6uCeiH Price USD: $0.1976 Price: 0.001165 SOL FDV: $197,621,954 Total liquidity: $82,041 Pooled BlockMind: 207,612 Pooled SOL: 241.9356 ($41,036) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

18 Feb 2025, 13:48 UTC845 viewsread 7 August 2026

🌱 New Pair on Solana: ARA - ARA / SOL 📍 DEX: Solana / Raydium Token address: 2iUbZtVicdmhqb12H3Q9CvFzSr6VDKQvZDRffTfFVQEw Price USD: $0.1104 Price: 0.0006518 SOL FDV: $110,499,221 Total liquidity: $61,346 Pooled ARA: 277,935 Pooled SOL: 180.7149 ($30,609) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

18 Feb 2025, 13:48 UTC500 views1 reactionsread 7 August 2026

🌱 New Pair on Solana: SpaceX - SPACEX / SOL 📍 DEX: Solana / Raydium Token address: 3oLyZwByapThF3TjN9hShpYWfyHUUzR63ozmk3JW5YqS Price USD: $0.02487 Price: 0.0001467 SOL FDV: $248,701,254 Total liquidity: $92,035 Pooled SPACEX: 1,852,662 Pooled SOL: 271.1129 ($45,962) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

👍1

18 Feb 2025, 13:48 UTC333 viewsread 7 August 2026

🌱 New Pair on Base: DeepSeek - DeepSeek / WETH 📍 DEX: Base / Uniswap Token address: 0x26a7D81c629b7a438A0b907074991B07bE04C712 Price USD: $0.0000002948 Price: 0.0000000001091 WETH FDV: $1,651 Total liquidity: $1,036 Pooled DeepSeek: 1,757,515,107 Pooled WETH: 0.1918 ($518) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

18 Feb 2025, 13:48 UTC254 views0 reactionsread 7 August 2026

🌱 New Pair on Sonic: BNB Agents - BNBAI / wS 📍 DEX: Sonic / Equalizer Token address: 0xe04dC3D8D16aA42351e2026071af667bf77E1a76 Price USD: $0.0000009044 Price: 0.000001527 wS FDV: $904 Total liquidity: $1,035 Pooled BNBAI: 597,701,084 Pooled wS: 836.5385 ($495) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

18 Feb 2025, 13:48 UTC215 viewsread 7 August 2026

🌱 New Pair on Unichain: FC - FC / WETH 📍 DEX: Unichain / Uniswap Token address: 0x0DA92F4DE3d9B1079787cd21cE159d3b6706E0C1 Price USD: $0.000002659 Price: 0.0000000009844 WETH FDV: $26,591 Total liquidity: $26,590 Pooled FC: 9,999,999,899 Pooled WETH: 0.0000001 ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

18 Feb 2025, 13:47 UTC183 views1 reactionsread 7 August 2026

🌱 New Pair on Solana: Grok City - GC / SOL 📍 DEX: Solana / FluxBeam Token address: 5rKou58srTSHDDPaTS9xo3xUrU93AU4AxKbpXvkuioW8 Price USD: $0.0003534 Price: 0.000002084 SOL FDV: $353,108 Total liquidity: $19,369 Pooled GC: 48,944,751 Pooled SOL: 12.2 ($2,069) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

🔥1

18 Feb 2025, 13:47 UTC143 viewsread 7 August 2026

🌱 New Pair on Solana: ValentAIn - VAL / SOL 📍 DEX: Solana / Raydium Token address: 63YbnczdKfS3y5t6X2dM6GprRLG6m6sjhi5j1KoYSbhr Price USD: $0.0001704 Price: 0.000001005 SOL FDV: $170,415 Total liquidity: $43,468 Pooled VAL: 127,598,581 Pooled SOL: 128.2421 ($21,744) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

18 Feb 2025, 13:47 UTC131 viewsread 7 August 2026

🌱 New Pair on Solana: EagleCoin - EAGLZ / SOL 📍 DEX: Solana / FluxBeam Token address: GkMkp7zaKTbX2pUgHPXT8rbbPsL7vB4wx5ksQyu2XkRt Price USD: $0.02488 Price: 0.0001469 SOL FDV: $248,899,619 Total liquidity: $4,149 Pooled EAGLZ: 73,074 Pooled SOL: 13.76 ($2,330) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

18 Feb 2025, 13:47 UTC116 viewsread 7 August 2026

🌱 New Pair on Solana: Tron Bull - Tron Bull / SOL 📍 DEX: Solana / FluxBeam Token address: Ccf8HPuDvXCiFmFBmAcMrNvd4hUif4nq7gxg4meizv4Q Price USD: $0.00001019 Price: 0.00000006016 SOL FDV: $8,460 Total liquidity: $9,273 Pooled Tron Bull: 452,983,467 Pooled SOL: 27.4908 ($4,656) ⚠️ WARNING: buying new pairs is extremely risky, please read pinned message before proceeding!

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

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

“New Pairs - DEX Screener” (@DSNewPairs), 2,311 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/DSNewPairs.

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.