Telegram RegisterThe public register of Telegram
Telegram profile photo for Data Lake Community

Supergroup

Data Lake Community

@DataLakeCommunity

Has discussion group

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

3,008members

-376 since we began measuring on 7 August 2026

45 online right now

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

Register entry

Telegram ID-1001561341298
TypeSupergroup
Username@DataLakeCommunity
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live24 October 2026
Measurements held22
Confirmed unchanged1 time, most recently 24 October 2026
On Telegramt.me/DataLakeCommunity

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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,0083,3843,1967 August 2026 — 3,384 members7 August 2026 — 3,382 members10 August 2026 — 3,365 members14 August 2026 — 3,332 members17 August 2026 — 3,306 members20 August 2026 — 3,289 members24 August 2026 — 3,267 members27 August 2026 — 3,249 members30 August 2026 — 3,219 members2 September 2026 — 3,195 members5 September 2026 — 3,181 members10 September 2026 — 3,181 members10 September 2026 — 3,161 members14 September 2026 — 3,137 members18 September 2026 — 3,119 members28 September 2026 — 3,084 members5 October 2026 — 3,053 members12 October 2026 — 3,029 members15 October 2026 — 3,024 members18 October 2026 — 3,017 members21 October 2026 — 3,013 members24 October 2026 — 3,008 members7 August 202624 October 2026
22 measurements spanning 78 days, net -376. 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 2,952–3,440 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 22
Measured (UTC)MembersChange
24 Oct 2026, 00:063,008-5
21 Oct 2026, 03:143,013-4
18 Oct 2026, 04:563,017-7
15 Oct 2026, 04:483,024-5
12 Oct 2026, 11:443,029-24
5 Oct 2026, 17:203,053-31
28 Sept 2026, 13:203,084-35
18 Sept 2026, 12:203,119-18
14 Sept 2026, 10:593,137-24
10 Sept 2026, 16:173,161-20
10 Sept 2026, 00:463,181no change
5 Sept 2026, 23:583,181-14
2 Sept 2026, 07:243,195-24
30 Aug 2026, 10:373,219-30
27 Aug 2026, 02:183,249-18
24 Aug 2026, 04:343,267-22
20 Aug 2026, 21:083,289-17
17 Aug 2026, 20:033,306-26
14 Aug 2026, 16:063,332-33
10 Aug 2026, 23:433,365first 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 24 October 2026 — this entry's latest reading, not the date you are reading this.

“Data Lake Community” (@DataLakeCommunity), 3,008 members as measured 24 October 2026. Telegram Register, tgregister.com/channel/DataLakeCommunity.

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.