24 Aug 2026, 17:14 UTC18 viewsread 26 August 2026
Posted without readable text
Signed 𝑯𝒂𝒎𝒎𝒂𝒅𝒊🇱🇾
Channel
ݺ،الفاخٰري .
@B_m17
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
690subscribers
-6 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001931104725 |
|---|---|
| Type | Channel |
| Username | @B_m17 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/B_m17 |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 13:01 | 690 | -6 |
| 4 Sept 2026, 01:19 | 696 | -2 |
| 27 Aug 2026, 04:58 | 698 | +2 |
| 26 Aug 2026, 17:32 | 696 | first reading |
Engagement
20 posts held, back to 22 November 2024 — 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 20 posts for this entry, the most recent from 24 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
10 Jul 2026, 11:45 UTC528 viewsread 26 August 2026
____
Signed 𝑯𝒂𝒎𝒎𝒂𝒅𝒊🇱🇾
25 Jun 2026, 18:08 UTC760 viewsread 26 August 2026
إذا وصلت إلى مرحلة أنك ترى وتعرف كل شيء ولكنك تظهر لهم أنك لم تفهم شيء .. فأنت حتما فهمت الحياة .🦅
Signed 𝑯𝒂𝒎𝒎𝒂𝒅𝒊🇱🇾
11 Apr 2026, 09:22 UTC≈1,000 viewsread 26 August 2026
____
Signed 𝐵𝐴𝑆𝐻𝑙𝑅 ⚠️ .
24 Jan 2026, 09:50 UTC≈1,630 viewsread 26 August 2026
والفكرة المريحة لديّ أن قلبي لا يضرّ أحدًا، أمشي في مناكب الأرض مُحسنًا ولو لم ألقَ إحسانًا، فإني أنتظر العوض مِن الله، ولا أطلب شيئًا مِن سواه.🤍
10 Jan 2026, 13:13 UTC≈1,650 viewsread 26 August 2026
هدفي في الحياه اني نكون احسن من امس مش احسن منك 🖤🖐🏻. 𝑀𝑌 𝑔𝑜𝑎𝑙 𝑖𝑛 𝑙𝑖𝑓𝑒 𝑖𝑠 𝑡𝑜 𝑏𝑒 𝑏𝑒𝑡𝑡𝑒𝑟 𝑡ℎ𝑎𝑛 𝐼 𝑤𝑎𝑠 𝑦𝑒𝑠𝑡𝑒𝑟𝑑𝑎𝑦 𝑛𝑜𝑡 𝑏𝑒𝑡𝑡𝑎𝑛 𝑡ℎ𝑎𝑛 𝑦𝑜𝑢.
Signed 𝑯𝒂𝒎𝒎𝒂𝒅𝒊🇱🇾
7 Jan 2026, 03:15 UTC≈1,490 viewsread 26 August 2026
كــــن لنفسك سنداً فالجميع حڪــــــايه وتنتهي🖤 ᵇᵉ ʸᵒᵘʳˢᵉˡᶠ ᵉᵛᵉʳʸᵒⁿᵉ ⁱˢ ᵃ ˢᵗᵒʳʸ ᵃⁿᵈ ⁱᵗ ᵉⁿᵈˢ
Signed 𝑯𝒂𝒎𝒎𝒂𝒅𝒊🇱🇾
17 Nov 2025, 00:40 UTC≈1,530 viewsread 26 August 2026
____
Signed 𝗕𝗔𝗦𝗛𝗜𝗥🇱🇾.
17 Nov 2025, 00:39 UTC≈1,870 viewsread 26 August 2026
الي يشيله البحر يرده الموج .
Signed 𝗕𝗔𝗦𝗛𝗜𝗥🇱🇾.
11 Nov 2025, 20:33 UTC≈1,550 viewsread 26 August 2026
____
Signed 𝗕𝗔𝗦𝗛𝗜𝗥🇱🇾.
11 Nov 2025, 20:11 UTC≈1,920 viewsread 26 August 2026
قائد وليس مقاد،وإن لم تكن سيد اللعبة إعتزل .
Signed 𝗕𝗔𝗦𝗛𝗜𝗥🇱🇾.
5 Oct 2025, 09:55 UTC≈2,120 viewsread 26 August 2026
لا يلوي ذراعي الا شديد ولا شديد إلا الله ☝️🏼.
Signed 𝗕𝗔𝗦𝗛𝗜𝗥🇱🇾.
Showing the 12 most recent of 20 posts we hold for @B_m17. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“ݺ،الفاخٰري .” (@B_m17), 690 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/B_m17.
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.