Messages in this channel will be automatically deleted after 1 day
Channel
،
@c_of_b
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001150946965 |
|---|---|
| Type | Channel |
| Username | @c_of_b |
| Created | Between 1 November 2019 and 31 December 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/c_of_b |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 01:00 | 1 | no change |
| 6 Aug 2026, 18:06 | 1 | first reading |
Engagement
19 posts held, back to 1 November 2023 — 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 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 19 posts for this entry, the most recent from 14 February 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 418
- Videos
- 32
- Links
- 17
Lifetime counters from Telegram’s own channel header, read 15 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.
- Video runtime
- 44s
- Average length
- 44s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
Channel name was changed to «،»
Channel photo removed
رسميه
https://t.me/madadsto
https://t.me/madadsto/3476
https://t.me/madadsto
زَيِّن بيتك بركنٍ رمضاني 🌙 كما تتزين الأفئدة فرحًا بقدوم أعظم الشهور، ندعوكم لإضفاء لمسة روحانية على منازلكم عبر تزيين ركن رمضاني خاص يعكس ذوقكم وفنكم الإيماني. مسابقة أجمل ركن رمضاني 📢 شاركوا في المسابقة بتصميم ركن رمضاني يضم أحد منتجات متجر مدد، والتقطوا له صورة جميلة، ثم أرسلوها لنا لدخول القرعة الرمضانية على أجمل تصميم. 🗳️ طريقة المشاركة: سيتم التصويت على المشاركات عبر التليجرام، والفائز سيكون من يحصل على أعلى…
سينطلق تحدي يغير بإذن الله وتحت عنايه امام الزمان ع من حياتكِ للخمسين يوم القادمة @madad_store
مُشاركة متجر مَدد في بازار الليالي الفاطمية ، الرواية الثانية لعام ١٤٤٥ هجري🖤 كلّية طب الأسنان ، جامِعة كربلاء . مع نَصب الخَيمة الفاطمية التي فيها الكثير من الأسرار والحكايا التي تنيرُ أرواحَ داخليها ..🤍 صَلّى اللهُ عليكِ فاطِمة .
غدا موعدنا مع طالبات جامعة كربلاء ببركة السيدة زينب عليها السلام لطفا ساهموا بالنشر
@madad_store
Showing the 12 most recent of 19 posts we hold for @c_of_b. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@c_of_b named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 15 August 2026 – 15 August 2026
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“،” (@c_of_b), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/c_of_b.
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.