Telegram RegisterThe public register of Telegram
Telegram profile photo for Facebook Leaks

Channel

Facebook Leaks

@fbleaks

On this record: Topic · Growth · Engagement · Referenced elsewhere · Cite this entry

1,164subscribers

-15 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001601546932
TypeChannel
Username@fbleaks
CreatedBetween 1 November 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 October 2026
Last confirmed live12 October 2026
Measurements held13
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/fbleaks

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

1,1641,1801,1727 August 2026 — 1,179 subscribers11 August 2026 — 1,180 subscribers15 August 2026 — 1,176 subscribers21 August 2026 — 1,175 subscribers24 August 2026 — 1,173 subscribers27 August 2026 — 1,172 subscribers2 September 2026 — 1,171 subscribers6 September 2026 — 1,172 subscribers15 September 2026 — 1,174 subscribers27 September 2026 — 1,170 subscribers5 October 2026 — 1,170 subscribers5 October 2026 — 1,169 subscribers12 October 2026 — 1,164 subscribers7 August 202612 October 2026
13 measurements spanning 65 days, net -15. 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 1,162–1,182 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 06:021,164-5
5 Oct 2026, 09:561,169-1
5 Oct 2026, 03:431,170no change
27 Sept 2026, 08:591,170-4
15 Sept 2026, 04:581,174+2
6 Sept 2026, 13:581,172+1
2 Sept 2026, 09:471,171-1
27 Aug 2026, 17:551,172-1
24 Aug 2026, 10:331,173-2
21 Aug 2026, 04:331,175-1
15 Aug 2026, 03:061,176-4
11 Aug 2026, 15:031,180+1
7 Aug 2026, 21:061,179first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Hacker News

This handle was named once in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.

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

“Facebook Leaks” (@fbleaks), 1,164 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/fbleaks.

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.