Telegram RegisterThe public register of Telegram
Telegram profile photo for BTC DZ

Channel

BTC DZ

@btcDZ16

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

7subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001504974505
TypeChannel
Username@btcDZ16
DescriptionLe minage du BTC DZ
Created23 September 2021 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live8 October 2026
Measurements held2
On Telegramt.me/btcDZ16

Growth

77 August 2026 — 7 subscribers12 August 2026 — 7 subscribers7 August 202612 August 2026
2 measurements spanning 6 days. 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 6–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 16:467no change
7 Aug 2026, 01:127first reading

Engagement

12 posts held, back to 23 September 2021 — 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 12 posts for this entry, the most recent from 6 October 2021. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
3

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

6 Oct 2021, 22:15 UTC60 viewsread 12 August 2026

أسرع طريقة تعدين بيتكوين مجاني 24/24 ⛏️⛏️ ساعة واش راك تستنى باش دير دراهم كي الناس 😍😍 فقط ادخل عبر تيليغرام http://t.me/CryptoTab_Official_Pool_Bot?start=1913052282

23 Sept 2021, 18:30 UTC69 viewsread 12 August 2026

اضغط الرابط و ابدأ الربح من التعدين 24/24⛏️⛏️

23 Sept 2021, 16:32 UTC58 viewsread 12 August 2026

Earn up to 1 BTC every month!. http://t.me/CryptoTab_Official_Pool_Bot?start=1913052282

Showing the 12 most recent of 12 posts we hold for @btcDZ16. 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.

Mentions

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.

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

“BTC DZ” (@btcDZ16), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/btcDZ16.

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.