Channel
@leak_db2
On this record: Topic · Growth · Engagement · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
426subscribers
+61 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002943814942 |
|---|---|
| Type | Channel |
| Username | @leak_db2 |
| Created | 21 August 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/leak_db2 |
Hacking & security — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 34% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 11:47 | 426 | +11 |
| 28 Oct 2026, 13:58 | 415 | +2 |
| 20 Oct 2026, 14:11 | 413 | +5 |
| 14 Oct 2026, 15:20 | 408 | +4 |
| 7 Oct 2026, 05:16 | 404 | +5 |
| 25 Sept 2026, 09:37 | 399 | +3 |
| 12 Sept 2026, 01:01 | 396 | +8 |
| 4 Sept 2026, 06:00 | 388 | +10 |
| 28 Aug 2026, 12:15 | 378 | +7 |
| 22 Aug 2026, 10:17 | 371 | +3 |
| 14 Aug 2026, 20:35 | 368 | +3 |
| 8 Aug 2026, 06:31 | 365 | no change |
| 7 Aug 2026, 11:33 | 365 | first reading |
7 posts held, back to 21 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 7 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
We are witnessing that some opportunistic individuals in the market are attempting to manipulate the real prices of accesses. For example, they list valuable accesses at extremely low prices. Sellers in the markets are generally divided into three groups: 📍Specialists 📍Broker sellers 📍Thieves — individuals who steal specialists’ accesses We hereby announce that such individuals will achieve nothing, and prices must…
🚨 Join This 2 Link 🚨 ———========= t.me/D3ltaboys_Market ==============———— ———====== https://t.me/+z21pfBkEDb00ODQ0 =======————
join here: https://t.me/+z21pfBkEDb00ODQ0
Sell And Support @leaker_db
Where did you hear about us?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
join to Market New link on Market : https://t.me/+z21pfBkEDb00ODQ0 Dont Left From Here Its Backup Channel Join on all channels ——————— Our previous channels were "b l o c k e d" by Telegram, and we are now rebuilding our community. Please invite your friends to join and make sure you are subscribed to all of our official channels to stay updated and connected. Admin 🚬 : @leaker_db
Channel created
Showing the 7 most recent of 7 posts we hold for @leak_db2. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Where did you hear about us?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 7 most recent posts we hold, published 21 August 2025 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Named by 2 registered channels — 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.
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.
@leak_db2 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Delta Boys” (@leak_db2), 426 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/leak_db2.
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.