Telegram RegisterThe public register of Telegram

Channel

بيتكوين العرب

@btcicoarab

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

422subscribers

+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-1001153329554
TypeChannel
Username@btcicoarab
Created18 June 2020measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/btcicoarab

Growth

4227 Aug 2026, 20:29 — 422 subscribers8 Aug 2026, 05:31 — 422 subscribers7 Aug 2026, 20:298 Aug 2026, 05:31
2 measurements taken within a single day. 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 421–423 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 05:31422no change
7 Aug 2026, 20:29422first reading

Engagement

2 posts held, back to 18 June 2020the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 2 posts for this entry, the most recent from 27 June 2020. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 8 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

27 Jun 2020, 09:10 UTC≈7,340 viewsread 8 August 2026

سنركز في هذه المرحلة على تحسين المحتوى و تطويره وقروب البيع و الشراء مستمر كما هو وأفضل بإذن الله بالإضافة للموقع ————— ♦️ احذر من اي شخص يتواصل معك بالخاص ويدعى انه من بيتكوين العرب.... لا نتواصل بالخاص مع أي شخص -------- مستمرين كما عودناكم في تقديم المحتوى و كل ما يخص العملات الرقمية عبر القنوات التالية الموقع الالكتروني https://arab-btc.net/ حساب تويتر: http://twitter.com/arab_btc ✅ لمتابعة آخر الأخبار والمقا

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

“بيتكوين العرب” (@btcicoarab), 422 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/btcicoarab.

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.