Channel
@xltiy
On this record: Topic · Growth · Engagement · What this channel posts · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
26,876subscribers
+344 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001401695651 |
|---|---|
| Type | Channel |
| Username | @xltiy |
| Created | Between 1 January 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 41 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/xltiy |
Personal blog — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Oct 2026, 12:06 | 26,876 | +13 |
| 24 Oct 2026, 10:05 | 26,863 | -4 |
| 23 Oct 2026, 09:08 | 26,867 | +3 |
| 22 Oct 2026, 09:30 | 26,864 | +28 |
| 21 Oct 2026, 02:50 | 26,836 | +17 |
| 20 Oct 2026, 02:47 | 26,819 | -1 |
| 19 Oct 2026, 05:57 | 26,820 | -219 |
| 18 Oct 2026, 05:46 | 27,039 | +260 |
| 17 Oct 2026, 02:19 | 26,779 | +24 |
| 16 Oct 2026, 05:20 | 26,755 | +6 |
| 15 Oct 2026, 05:57 | 26,749 | -2 |
| 14 Oct 2026, 02:55 | 26,751 | -12 |
| 11 Oct 2026, 13:19 | 26,763 | +24 |
| 7 Oct 2026, 04:18 | 26,739 | -62 |
| 2 Oct 2026, 08:18 | 26,801 | +54 |
| 18 Sept 2026, 17:01 | 26,747 | +4 |
| 16 Sept 2026, 12:17 | 26,743 | +29 |
| 14 Sept 2026, 13:20 | 26,714 | +15 |
| 12 Sept 2026, 20:40 | 26,699 | +22 |
| 7 Sept 2026, 15:17 | 26,677 | first reading |
58 posts held, back to 15 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 110 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 23 October 2026 |
|---|---|
| Posts held | 58 (15 June 2026 – 23 October 2026) |
| Views total | 104,429 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Oct 2026, 08:52 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @xltiy. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 58 most recent posts we hold for this entry, published 15 June 2026 to 23 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
في يوِم مِن الأيَامُ سِنجلٓسُ أمامَ بعَضِنا بأخرَ أليوم أنتِ تُحكِي ليَ عنِ تعبِك وأنا أحِكي لكَ تعبَيِ فِي يومَ مَن الأيَامُ سيَحرصُ كلَانا أن يعوُدَ إلى البَيت لنِحتَمي ببَعضَنا وَتهدأ اللَياليِ بِنا فِي يوَم مِن الأيامُ سَتختفِي المٓسافة التَي بِيننَا وَسنكوَن معًا فِي يومَ من الأيَام سَيكون الزَمان مُنصفًا لنا ويَجمعُني بَك سَقفً واحد .
Photo, posted without a caption
انت يَمكن عَندي أغلى مِن الهَوى :
قُبلة باللسان قُبلة على الخدّين بين الشفتين أو فوقهما قُبلة على الجروح لماضيكِ، قُبلة لي ولك نتشاركها مَعًا نتذوّقها سَويًّا لجفنيك لدموعك لأَنك لم تُتركني ابدًا .
Photo, posted without a caption
هي هَتعدي بس هتأخذ منك شوية شغف ومشاعر .
أوعِدني إنّك فبُعدي عَنّك حَتفتكرني لَو عِشت تاني مع حُب تاني خلّيك فاكِرني خلّيك حَبيبي مِن غير مَنجرح بَعضنا خلّيك حَبيبي حتى وأنتَ مِش هنا بَلاش نضّيع ذكرى حِلوة فـ قلبنا أوعدني إنّك ببُعدي عَنّك حَتفتكرني
والله مادري شديصير بس لازم أكمل .
سَينتهي أَكتوبر وَأَنتَ ما زلتَ غائبًا ألا تُريد تحقيق الأَسطورة التي تَقول إنّ الغائبَ الأَحبِّ إلى قَلبك سَيعود في أَحد أيّام أكتوبر؟ فَأَين أَنتَ يا أَحبِّهم إلى قلبي، سارع بالعودة فَأَكتوبر يَمضي سَريعًا وَأَنا ما زلتُ أَنتظرك .
Photo, posted without a caption
تعال اليَ عندما تشعر أنك لستَ بخير سَوف أَعانقك وسَتشعر أنكَ في أمانِ حضن تعال إِلي اَقبلَكَ وأضمكَ بين أحضاني وسأقولَ للسماء حينها أنظروا قمركم بَين أحضاني.
Photo, posted without a caption
Showing the 12 most recent of 58 posts we hold for @xltiy. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 12 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 18 seed channels' Telegram-generated recommendation lists in total, of which the 17 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“مُمكن الك” (@xltiy), 26,876 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/xltiy.
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.