Telegram RegisterThe public register of Telegram
Telegram profile photo for Death overs prime leak

Channel

Death overs prime leak

@deathovers2

On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry

3,014subscribers

-70 since we began measuring on 25 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001613408777
TypeChannel
Username@deathovers2
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live17 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/deathovers2

Topic

Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 44% 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 why it has no browse page of its own yet.

Growth

3,0143,0843,04925 August 2026 — 3,084 subscribers25 August 2026 — 3,084 subscribers29 August 2026 — 3,077 subscribers31 August 2026 — 3,073 subscribers4 September 2026 — 3,056 subscribers10 September 2026 — 3,038 subscribers13 September 2026 — 3,029 subscribers17 September 2026 — 3,014 subscribers25 August 202617 September 2026
8 measurements spanning 23 days, net -70. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,004–3,095 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 13:393,014-15
13 Sept 2026, 12:393,029-9
10 Sept 2026, 03:363,038-18
4 Sept 2026, 17:573,056-17
31 Aug 2026, 18:573,073-4
29 Aug 2026, 00:033,077-7
25 Aug 2026, 22:453,084no change
25 Aug 2026, 22:303,084first reading

Engagement

20 posts held, back to 20 August 2025the 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 19 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

19 Aug 2026, 15:39 UTC525 viewsread 25 August 2026

https://t.me/+svo1kf7-d_9mMjk1 PRIVATE CONTEST STARTING SOON 🔜 STAY TUNED ❤️💸 SAFEST WAY TO PLAY FANTASY AND WIN LOTS OF MONEY 🔥💸 JOIN ⬇️ https://t.me/+svo1kf7-d_9mMjk1 JOIN THIS CHANNEL ⬆️ @Venommm07

28 Aug 2025, 12:40 UTC≈6,620 viewsread 25 August 2026
Photo

A23 FILED A CASE IN KARNATKA HIGH COURT. HEARING ON 30TH AUG.

28 Aug 2025, 04:11 UTC≈5,020 viewsread 25 August 2026
Photo

SOMETHING IS COOKING ❤️ DON'T LEAVE STAY TUNED ✅

22 Aug 2025, 06:59 UTC≈4,500 viewsread 25 August 2026

Aap logo ka pyar bana raha itne sallo se ushke liye bohot bohot dhanyawad 🙏❤️ But tension lene ka nahii bhagwan ek rasta band krta hai toh bohot se raste khol bhi deta haii 🤞🥰 Ham sath the aur rahenge 🌟❤️ Kuch unexpected ho sakta haii lets hope for best 💕 Don't leave channel wait for more updates ✅

Showing the 12 most recent of 20 posts we hold for @deathovers2. 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

@Cricinformer
@Cricinforrmerx · 45,458
Telegram ranks this channel #5 of 49 here — alongside 48 others — read 27 August 2026
Dream11 Teams ( Free )
@Dream11Teamsfree8 · 47,925
Telegram ranks this channel #11 of 63 here — alongside 62 others — read 25 August 2026
Fantasycricketgeek (Peeyush Sharma)
@TheFantasycricketgeek · 45,728
Telegram ranks this channel #16 of 74 here — alongside 73 others — read 27 August 2026
INVESTOGENIE™ l SEBI ®️ RESEARCH ANALYST
@Investogenie · 44,032
Telegram ranks this channel #17 of 62 here — alongside 61 others — read 27 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Death overs prime leak” (@deathovers2), 3,014 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/deathovers2.

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.