🇩🇪 TRENT 🇩🇪 WON THE TOSS & OPTED TO BOWL FIRST ✔️✔️

Channel
CRICKET MARKET LOAD🏏
@cricketmarketload7
On this record: Topic · Growth · Engagement · Posts · Cite this entry
659subscribers
-30 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 | -1002703047387 |
|---|---|
| Type | Channel |
| Username | @cricketmarketload7 |
| Created | Between 1 June 2025 and 23 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 2 times, most recently 19 November 2026 |
| On Telegram | t.me/cricketmarketload7 |
Topic
Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 13:36 | 659 | -3 |
| 26 Oct 2026, 10:30 | 662 | -2 |
| 13 Oct 2026, 21:44 | 664 | -5 |
| 3 Oct 2026, 19:55 | 669 | -5 |
| 18 Sept 2026, 04:21 | 674 | -2 |
| 9 Sept 2026, 16:15 | 676 | -3 |
| 31 Aug 2026, 06:55 | 679 | -2 |
| 23 Aug 2026, 16:48 | 681 | -2 |
| 16 Aug 2026, 02:24 | 683 | -6 |
| 8 Aug 2026, 02:20 | 689 | no change |
| 7 Aug 2026, 18:59 | 689 | first reading |
Engagement
20 posts held, back to 23 August 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 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 30 August 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
🇵🇰 PAKISTAN 🇵🇰 HAVE WON THE TOSS AND OPTED TO BOWL FIRST ✔️
🇩🇪 WELSH 🇩🇪 WON THE TOSS & OPTED TO BOWL FIRST ✔️✔️
🇩🇪 WELSH W 🇩🇪 WON THE TOSS & OPTED TO BAT FIRST ✔️✔️
🇩🇪 TRENT 🇩🇪 WON THE TOSS & OPTED TO BOWL FIRST ✔️✔️
🇩🇪 TRENT W 🇩🇪 WIN ✔️✔️
ACCORDING TO BETFAIR LOAD MATCH WINNER - TRENT WOMEN🖤 BOOK SET 20-25 PAISA
🇩🇪 BIRMINGHAM - W 🇩🇪 WON THE TOSS AND DECIDED TO BAT ✔️✔️
🇩🇪 MANCHESTER 🇩🇪 WON THE TOSS & OPTED TO BOWL FIRST ✔️✔️
🇩🇪 NORTHERN W 🇩🇪 WIN ✔️✔️
ACCORDING TO BETFAIR LOAD MATCH WINNER - NORTHERN WOMEN🖤 BOOK SET 20-25 PAISA
🇩🇪 NORTHERN - W 🇩🇪WON THE TOSS AND DECIDED TO BAT ✔️✔️
Showing the 12 most recent of 20 posts we hold for @cricketmarketload7. 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 November 2026 — this entry's latest reading, not the date you are reading this.
“CRICKET MARKET LOAD🏏” (@cricketmarketload7), 659 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/cricketmarketload7.
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.