يربطني بك شيء أعمق من المحبة ، أعجز عن شرح الأمر لك لكنني بطريقةٍ ما أشعر أنك أنا♥️

Channel
حُـــب
@miolv22
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
6,100subscribers
-63 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001212806704 |
|---|---|
| Type | Channel |
| Username | @miolv22 |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 24 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 24 September 2026 |
| On Telegram | t.me/miolv22 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 35% 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 |
|---|---|---|
| 24 Sept 2026, 21:21 | 6,100 | -9 |
| 16 Sept 2026, 15:19 | 6,109 | -5 |
| 12 Sept 2026, 12:58 | 6,114 | -9 |
| 8 Sept 2026, 02:17 | 6,123 | -7 |
| 2 Sept 2026, 16:48 | 6,130 | -3 |
| 30 Aug 2026, 11:37 | 6,133 | -6 |
| 27 Aug 2026, 08:03 | 6,139 | +2 |
| 20 Aug 2026, 19:17 | 6,137 | -13 |
| 17 Aug 2026, 13:36 | 6,150 | -4 |
| 14 Aug 2026, 15:55 | 6,154 | -7 |
| 11 Aug 2026, 11:46 | 6,161 | -2 |
| 11 Aug 2026, 09:17 | 6,163 | first reading |
Engagement
15 posts held, back to 5 July 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3 pages 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 15 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
"إخترتك العُمر ، يوم إن العُمر مرة كنت الصّحيح الوحيد من إختياراتي♥️"
أحبك بهدوء، لكن بداخلي ضجيج كامل باسمك ♥️
في زحمة العالم، قلبي يعرفك من بين الجميع♥️
عسى ربي مايكتب في حبنا نهاية وتعيش لي واعيش لك كل العمر♥️
"بيني وبينك شعور لا يحتاج تفسير، يكفي أنه يسكنني"♥️
الحب أن تُرهقان بعض لكن لا احَد يتخلى♥️
صبّحت بالحب يَ طاَرِي الخير كله يَ زينّ يُومِي وانتِ سَيدّة صباَحاتي..♥️
صَبحْت بآلحبْ يَ شخصٍ عن ألفِ شخصٍ عن ألف معنى وألف حُب♥️
انت تعني لي العالم وانا لا أتخلى عن عالمي♥️
صباحي وجهك اللي كل ما اشوفه أحس ان الأيام والزمان بخير ♥️
صباح الخير أمّا بعد : يا ملجأ رُوحي يا كُل الأشياء التي تُناسبني تمامًا♥️
Showing the 12 most recent of 15 posts we hold for @miolv22. 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
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@BC_ah13 · 25,826
Telegram ranks this channel #3 of 73 here — alongside 72 others — read 18 September 2026
@BC_O707 · 23,222
Telegram ranks this channel #3 of 81 here — alongside 80 others — read 18 September 2026
@eurs4 · 20,753
Telegram ranks this channel #4 of 69 here — alongside 68 others — read 26 September 2026
@adub121 · 37,839
Telegram ranks this channel #6 of 70 here — alongside 69 others — read 31 August 2026
@u1_7z · 65,880
Telegram ranks this channel #19 of 35 here — alongside 34 others — read 22 August 2026
@zoze500 · 31,008
Telegram ranks this channel #33 of 86 here — alongside 85 others — read 7 September 2026
@fraindz · 272,420
Telegram ranks this channel #41 of 76 here — alongside 75 others — read 11 August 2026
@DT_0G · 22,986
Telegram ranks this channel #46 of 61 here — alongside 60 others — read 19 September 2026
This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“حُـــب” (@miolv22), 6,100 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/miolv22.
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.