Channel
@NewContractsOnARB
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002196664309 |
|---|---|
| Type | Channel |
| Username | @NewContractsOnARB |
| 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/NewContractsOnARB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:18 | 10 | no change |
| 8 Aug 2026, 18:49 | 10 | first reading |
20 posts held, back to 7 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.
Deployer Wallet: 0.00 ETH - Arbiscan Token: Ting Ting Coin (TTC) - Arbiscan Contract: 0x0e8b31bba82ffdca2664331b7425d7e7d0346161 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.06 ETH - Arbiscan Token: ETH (ETH) - Arbiscan Contract: 0xaac032987f8042dac6278484f32df0ddc76c6875 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.06 ETH - Arbiscan Token: USDC.e (USDC.е) - Arbiscan Contract: 0xfffa1631818d43cf9c6c1a88543291c42d81beb5 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.06 ETH - Arbiscan Token: USDC (USDC) - Arbiscan Contract: 0x2b3c2edd5cfc1e6565e8a4a74db1011fde0f7e59 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.06 ETH - Arbiscan Token: USDT (USDT) - Arbiscan Contract: 0x5b028e5af6b7d102a93e3a9cef80330e2ee75e48 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.00 ETH - Arbiscan Token: khoshk (khs) - Arbiscan Contract: 0x5ccdb41739c90fca6b3772f43796c1dd5ac31949 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.01 ETH - Arbiscan Token: OpenMind (OENMD) - Arbiscan Contract: 0x4ca75cd665cf5a3bb28e787c3c8846152063dbb4 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.06 ETH - Arbiscan Token: ꓪᏴꓔᏟ (ꓪᏴꓔᏟ) - Arbiscan Contract: 0xfa87d93a42c98461cdfd21a6487d05fe68bbc020 Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.06 ETH - Arbiscan Token: USDC.e (USDC.е) - Arbiscan Contract: 0x9d364a3b95402a25dde07a741d87290031a2a58b Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.06 ETH - Arbiscan Token: USDT (USDT) - Arbiscan Contract: 0x401f08c2fc3ecdca5a11c39bc582bb1301ddae9f Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.06 ETH - Arbiscan Token: ETH (ETH) - Arbiscan Contract: 0x9b052705d0fc0f1ef9fa38973c63e4b7a7ad48ba Maestro (Pro) • DexView • DexScreener • Community We're looking for new shillers & partners - More Info
Deployer Wallet: 0.06 ETH - Arbiscan Token: USDC (USDC) - Arbiscan Contract: 0x2d98e04aa99cd4e6833ba6ddc65b421275b09db4 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 @NewContractsOnARB. 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.
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 Contracts ARB - Arbitrum” (@NewContractsOnARB), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/NewContractsOnARB.
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.