Telegram RegisterThe public register of Telegram
Telegram profile photo for BLPlace files

Channel

BLPlace files

@blplace_files

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

1,681subscribers

+37 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-1002780804329
TypeChannel
Username@blplace_files
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 September 2026
Last confirmed live10 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/blplace_files

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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,6441,6811,662.57 August 2026 — 1,644 subscribers8 August 2026 — 1,647 subscribers11 August 2026 — 1,655 subscribers14 August 2026 — 1,659 subscribers17 August 2026 — 1,654 subscribers20 August 2026 — 1,656 subscribers24 August 2026 — 1,657 subscribers27 August 2026 — 1,660 subscribers31 August 2026 — 1,655 subscribers3 September 2026 — 1,661 subscribers8 September 2026 — 1,654 subscribers13 September 2026 — 1,662 subscribers17 September 2026 — 1,665 subscribers25 September 2026 — 1,665 subscribers25 September 2026 — 1,670 subscribers4 October 2026 — 1,677 subscribers10 October 2026 — 1,681 subscribers7 August 202610 October 2026
17 measurements spanning 64 days, net +37. 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,638–1,687 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 22:391,681+4
4 Oct 2026, 23:211,677+7
25 Sept 2026, 10:421,670+5
25 Sept 2026, 02:381,665no change
17 Sept 2026, 09:161,665+3
13 Sept 2026, 04:171,662+8
8 Sept 2026, 22:361,654-7
3 Sept 2026, 10:051,661+6
31 Aug 2026, 00:241,655-5
27 Aug 2026, 23:461,660+3
24 Aug 2026, 19:361,657+1
20 Aug 2026, 19:011,656+2
17 Aug 2026, 19:241,654-5
14 Aug 2026, 17:251,659+4
11 Aug 2026, 09:431,655+8
8 Aug 2026, 13:381,647+3
7 Aug 2026, 17:471,644first 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.

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

“BLPlace files” (@blplace_files), 1,681 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/blplace_files.

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.