8 Aug 2026, 02:28 UTC9 viewsread 8 August 2026
Forwarded from @THECHOSENFROGPhoto
Photo, posted without a caption
Channel
DUBX OFFICIAL PORTAL
@DUBXOFFICIALPORTAL
On this record: Growth · Engagement · Posts · Citations · Cite this entry
635subscribers
-30 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001984294720 |
|---|---|
| Type | Channel |
| Username | @DUBXOFFICIALPORTAL |
| Created | Between 1 April 2023 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/DUBXOFFICIALPORTAL |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 02:58 | 635 | -5 |
| 29 Aug 2026, 20:58 | 640 | -4 |
| 23 Aug 2026, 14:04 | 644 | -11 |
| 16 Aug 2026, 14:49 | 655 | -9 |
| 8 Aug 2026, 21:12 | 664 | -1 |
| 8 Aug 2026, 12:05 | 665 | first reading |
Engagement
20 posts held, back to 18 July 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 page of 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 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
8 Aug 2026, 01:46 UTC10 viewsread 8 August 2026
Forwarded from @THECHOSENFROG
Enjoy the ride anon It's just started
7 Aug 2026, 23:20 UTC13 viewsread 8 August 2026
Forwarded from @THECHOSENFROGPhoto
Few understand 💹
7 Aug 2026, 22:18 UTC14 viewsread 8 August 2026
Forwarded from @THECHOSENFROG
10M+
7 Aug 2026, 14:29 UTC10 viewsread 8 August 2026
Forwarded from @THECHOSENFROG
PEPE on ETH did billions. PEPE on SOL did $80M. PEPE on Robinhood Chain hasn't even started. Even a fraction of the SOL run puts this in the millions. If history rhymes even slightly, we're talking double-digit millions.
7 Aug 2026, 14:28 UTC9 viewsread 8 August 2026
Forwarded from @THECHOSENFROG
PEPE on ETH did billions. PEPE on SOL did $80M. PEPE on Robinhood Chain hasn't even started. Even a fraction of the SOL run puts this in the millions. If history rhymes even slightly, we're talking double-digit millions.
7 Aug 2026, 11:15 UTC19 viewsread 8 August 2026
I remember when PEPE launched on ETH did billions. I remember when PEPE launched on SOL hit $80M mcap. Now PEPE is on Robinhood Chain trading under 100K mcap. Never fade PEPE on any chain. This is the next runner. CA: 0x9B09c435BC5DA088722bE47E97989fB1e3Ed4eB9
7 Aug 2026, 10:44 UTC15 viewsread 8 August 2026
Forwarded from @RobinhoodTrenchersPhoto
Trencing no.27 on dex soon will be trending alongside $CASHCAT Ca: 0x9B09c435BC5DA088722bE47E97989fB1e3Ed4eB9
7 Aug 2026, 00:44 UTC16 viewsread 8 August 2026
https://t.me/THECHOSENFROG
6 Aug 2026, 21:59 UTC20 viewsread 8 August 2026
0x9B09c435BC5DA088722bE47E97989fB1e3Ed4eB9
4 Aug 2026, 13:56 UTC31 viewsread 8 August 2026
Cashcat Shilling Robinhood Trenches on X https://x.com/i/status/2084632891816808733
4 Aug 2026, 13:56 UTC34 viewsread 8 August 2026
Forwarded from @RobinhoodTrenchersPhoto
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @DUBXOFFICIALPORTAL. 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
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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“DUBX OFFICIAL PORTAL” (@DUBXOFFICIALPORTAL), 635 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/DUBXOFFICIALPORTAL.
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.