7 Aug 2026, 20:59 UTC5 viewsread 8 August 2026
📊 DAY RECAP · 07 Aug 2026 ────────────── No bets today yet.
Channel
🏴☠️PIRATES🏴☠️
@corsairsbet
On this record: Growth · Engagement · Posts · Cite this entry
255subscribers
-18 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001838966920 |
|---|---|
| Type | Channel |
| Username | @corsairsbet |
| Created | Between 1 October 2022 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 | 14 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/corsairsbet |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 23:01 | 255 | -1 |
| 8 Sept 2026, 07:01 | 256 | -5 |
| 29 Aug 2026, 11:57 | 261 | -6 |
| 21 Aug 2026, 13:46 | 267 | -3 |
| 14 Aug 2026, 02:35 | 270 | -3 |
| 8 Aug 2026, 08:47 | 273 | no change |
| 7 Aug 2026, 10:22 | 273 | first reading |
Engagement
20 posts held, back to 22 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
6 Aug 2026, 20:59 UTC18 viewsread 8 August 2026
📊 DAY RECAP · 06 Aug 2026 ────────────── No bets today yet.
5 Aug 2026, 20:59 UTC32 viewsread 8 August 2026
📊 DAY RECAP · 05 Aug 2026 ────────────── No bets today yet.
4 Aug 2026, 20:59 UTC39 viewsread 8 August 2026
📊 DAY RECAP · 04 Aug 2026 ────────────── No bets today yet.
3 Aug 2026, 20:59 UTC49 viewsread 8 August 2026
📊 DAY RECAP · 03 Aug 2026 ────────────── No bets today yet.
2 Aug 2026, 20:59 UTC57 viewsread 8 August 2026
📊 DAY RECAP · 02 Aug 2026 ────────────── No bets today yet.
1 Aug 2026, 20:59 UTC60 viewsread 8 August 2026
📊 DAY RECAP · 01 Aug 2026 ────────────── No bets today yet.
31 Jul 2026, 20:59 UTC70 viewsread 8 August 2026
➖ DAY RECAP · 31 Jul 2026 ────────────── 🎟 Bets: 1 · settled: 0 ✅ Won: 0 ❌ Lost: 0 ────────────── 💰 Profit: +0.00u 📊 ROI: +0.0% ────────────── ⏳ pending: 1
31 Jul 2026, 09:19 UTC75 viewsread 8 August 2026
Photo
🎯 Over 5.5 @ 1.85 💰 0.5 units
30 Jul 2026, 20:59 UTC65 viewsread 8 August 2026
📊 DAY RECAP · 30 Jul 2026 ────────────── No bets today yet.
29 Jul 2026, 20:59 UTC73 viewsread 8 August 2026
📊 DAY RECAP · 29 Jul 2026 ────────────── No bets today yet.
28 Jul 2026, 20:59 UTC79 viewsread 8 August 2026
📊 DAY RECAP · 28 Jul 2026 ────────────── No bets today yet.
Showing the 12 most recent of 20 posts we hold for @corsairsbet. 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“🏴☠️PIRATES🏴☠️” (@corsairsbet), 255 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/corsairsbet.
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.