Channel
@NewPairsOnARB
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
7subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002158636889 |
|---|---|
| Type | Channel |
| Username | @NewPairsOnARB |
| Description | New Contracts: @NewContractsOnETH @NewContractsOnBNB @NewContractsOnARB @NewContractsOnBonkFun @NewContractsOnPumpFun @NewContractsOnFourMeme New Pairs: @NewPairsOnETH @NewPairsOnBNB @NewPairsOnARB @NewPairsOnBonkFun @NewPairsOnPumpFun @NewPairsOnFourMeme |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/NewPairsOnARB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 17:46 | 7 | no change |
| 8 Aug 2026, 18:47 | 7 | first reading |
20 posts held, back to 5 December 2025 — 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.
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 8 December 2025. An engagement rate over an empty window would be a number about nothing.
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. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
DEX: SushiSwap V2 Token: OpenMind - Arbiscan Contract: 0x4ca75cd665cf5a3bb28e787c3c8846152063dbb4 Pair: OENMD / USDT - Arbiscan Contract: 0x52fb8e8ae17a9e5c521b3fd320f78eb8b2d51963 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: SushiSwap V2 Token: RGSDGC - Arbiscan Contract: 0xe2577d558cbe1f5e2a58a0f66a0c8ed62b5d51c0 Pair: RGSDGC / USDT - Arbiscan Contract: 0x736f033cfa27783e58fe5b663687d5fdaca6f7ee Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: PancakeSwap V3 Token: TEST ARB - Arbiscan Contract: 0x4ec04b3764c06735235cbe7096dec31f896f5db4 Pair: TARB / WETH - Arbiscan Contract: 0x7110b384b11f07f69c95f7e358afdccef5b7556e Pair Fee: 0.01% Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: SushiSwap V2 Token: LYS Labs - Arbiscan Contract: 0x99bff11ea90137972a15ca1c32fedb3a11204bd6 Pair: LYSL / USDT - Arbiscan Contract: 0xc1453e6dd072c0ec975b81e5c24b3ef033557410 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: UniSwap V3 Token: PayPal USD - Arbiscan Contract: 0x46850ad61c2b7d64d08c9c754f45254596696984 Pair: PYUSD / WETH - Arbiscan Contract: 0x077a590b7f39124edcd48c52c75d33142ab03754 Pair Fee: 0.30% Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: SushiSwap V3 Token: Leviathan - Arbiscan Contract: 0x8e59825515f1da6a3c3656a0a6b06b715f7fe360 Pair: WETH / LEV - Arbiscan Contract: 0x4a97a3eda37235b67be61a885f8c50bc76a3eb38 Pair Fee: 0.30% Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: SushiSwap V2 Token: Nevermined - Arbiscan Contract: 0xdf3498a703fb42c33e1253cbc7876915bbe4f3db Pair: NVMED / USDT - Arbiscan Contract: 0x8e4ba67a93baad9dd812a93c90cd1fdef2eddc8f Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: SushiSwap V2 Token: NBDOR - Arbiscan Contract: 0x24d71316f2219bbf50859fdce4ab73037b863c06 Pair: NBDOR / USDT - Arbiscan Contract: 0x68ae281329fef027316529ceff92f747374fe8fa Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: SushiSwap V2 Token: Tiger OG - Arbiscan Contract: 0xc91934f40ca98a4f24af3ffae2a6381a4a418f27 Pair: WETH / TigerOG - Arbiscan Contract: 0x6b634120acf1135b80c9615487e61e63b570622e Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: SushiSwap V2 Token: Frog OG - Arbiscan Contract: 0x50f346c35d0121e45823f3490857f03ffcaa6d71 Pair: FrogOG / WETH - Arbiscan Contract: 0x39161e717c80afc425af346c2b4e9cef9cacdc3a Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: SushiSwap V2 Token: Lion OG - Arbiscan Contract: 0x54a5cdba137286f6ad3f762e2165e613cb225215 Pair: LionOG / WETH - Arbiscan Contract: 0x3dac635373f21148e0d1b0b7ee8c3174161e1c5c Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
DEX: UniSwap V2 Token: Frog OG - Arbiscan Contract: 0x50f346c35d0121e45823f3490857f03ffcaa6d71 Pair: FrogOG / WETH - Arbiscan Contract: 0xe4cfc8744f2539d8154660346a752bb3be0333da Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Showing the 12 most recent of 20 posts we hold for @NewPairsOnARB. 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 — 1,163,668 of 1,481,217entries 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.
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.
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.
@NewPairsOnARB named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“New Pairs ARB - Arbitrum” (@NewPairsOnARB), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/NewPairsOnARB.
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.