Telegram RegisterThe public register of Telegram
Telegram profile photo for DataBase leaker

Channel

DataBase leaker

@leaker_database

On this record: Topic · Growth · Engagement · Posts · Cite this entry

17subscribers

+3 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-1001893142678
TypeChannel
Username@leaker_database
Created10 June 2023 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live20 November 2026
Measurements held4
Confirmed unchanged1 time, most recently 20 November 2026
On Telegramt.me/leaker_database

Topic

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 1 October 2026 and assigned it the closest of 31 fixed categories, at 82% 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

141715.58 August 2026 — 14 subscribers12 August 2026 — 14 subscribers26 September 2026 — 16 subscribers20 November 2026 — 17 subscribers8 August 202620 November 2026
4 measurements spanning 104 days, net +3. 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 14–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Nov 2026, 08:1817+1
26 Sept 2026, 00:0016+2
12 Aug 2026, 01:3014no change
8 Aug 2026, 06:4614first reading

Engagement

3 posts held, back to 10 June 2023 — 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 3 posts for this entry, the most recent from 13 November 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Nov 2025, 12:52 UTC156 views0 reactionsread 12 August 2026

join here to see sample "D B" https://t.me/+9K6McD1tqe1iNjE0

Showing the 3 most recent of 3 posts we hold for @leaker_database. 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 20 November 2026 — this entry's latest reading, not the date you are reading this.

“DataBase leaker” (@leaker_database), 17 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/leaker_database.

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.