دز نزوجك ع ذوق سبلوش عمتكم🍓🔥

Channel
عبارات | ليطمئن قلبي
@YYYXY
On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
1,085,698subscribers
-1,218 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
Register entry
| Telegram ID | -1001365722569 |
|---|---|
| Type | Channel |
| Username | @YYYXY |
| Description | [+] لطلب تمويل القنوات : @xxx1x [+] قناة التمويلات : @nnnon |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/YYYXY |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 69% 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 Aug 2026, 08:22 | 1,085,698 | -261 |
| 11 Aug 2026, 07:48 | 1,085,959 | -333 |
| 10 Aug 2026, 08:11 | 1,086,292 | -140 |
| 9 Aug 2026, 11:35 | 1,086,432 | -51 |
| 8 Aug 2026, 11:16 | 1,086,483 | -176 |
| 7 Aug 2026, 08:12 | 1,086,659 | -248 |
| 6 Aug 2026, 11:40 | 1,086,907 | -9 |
| 6 Aug 2026, 10:47 | 1,086,916 | first reading |
Engagement
836 posts held, back to 24 July 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 17 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.272%
- avg views ÷ 1,085,698 subscribers
- Avg views / post
- 2,960
- 836 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 836
- of 836 held
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 13 August 2026 |
|---|---|
| Posts held | 836 (24 July 2026 – 13 August 2026) |
| Views total | 2,472,215 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 00:50 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.
What this channel posts
- Photos
- 91
- Videos
- 1
- Links
- 6
Lifetime counters from Telegram’s own channel header, read 12 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.
View velocity
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 808 of this channel’s own posts over the last 30 days: across 4of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 13 hours of being posted; a typical post has already reached 8.64% of its 24-hour view count within the first hour, and 38.0% within the first six; the median 24-hour reach across those posts is 9,365 views — 0.863% of this channel’s own subscriber count (90th percentile 10,030).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /26308513 Aug 2026, 00:45 UTC | 15 minutes – 5 minutes old | 35 viewsno reaction reading | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /26308313 Aug 2026, 00:31 UTC | 119 minutes – 19 minutes old | 175 viewsno reaction reading | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /26308213 Aug 2026, 00:25 UTC | 125 minutes – 25 minutes old | 264 viewsno reaction reading | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /26308113 Aug 2026, 00:15 UTC | 1under a minute – under a minute old | 1 viewno reaction reading | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /26307913 Aug 2026, 00:00 UTC | 216 minutes – 50 minutes old | 457 viewsno reaction reading | no checkpoint reading yet | not yet at 24h | 23 minutesprovisional — final view count still climbing |
| /26307812 Aug 2026, 23:55 UTC | 120 minutes – 20 minutes old | 226 viewsno reaction reading | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /26307612 Aug 2026, 23:31 UTC | 19 minutes – 9 minutes old | 134 viewsno reaction reading | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /26307512 Aug 2026, 23:30 UTC | 210 minutes – 45 minutes old | 448 viewsno reaction reading | no checkpoint reading yet | not yet at 24h | 16 minutesprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Recent posts
https://t.me/+m5SKtTVCsloxMzIy
كروب المناقيل صاعد بحث تعالو 😂
اصعدو تصال راح تبلش الفقرلت والمسابقات على جوائز 🌚
https://t.me/mnagele
آدم يكول اريد مشرفين مرتبين يمي .
آدم يكول اريد مشرفين مرتبين يمي .
https://t.me/+1IE4-ggwdhJlMDUy
توت مشمش ، سوسه ، توت ، سدن ، نسنس ، ديا ، سوسه ، ساره ، ميس ، فطمي ، زينب ، شهد ، كندر ، و99 أخرون يردوك بلچات حبيبي 🍒
https://t.me/+SbVkDWQSdmw3OWIy
گروب لارين رجع ع الساحه بقيادة نيترو ادام الله ضله ،🚬
https://t.me/+CqqOzDSQamVmZGRi
Showing the 12 most recent of 836 posts we hold for @YYYXY. 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.
Posts edited after publishing
@YYYXY edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 8 August 2026
- Most recent edit
- 8 August 2026
Citation-graph rank
Citation-graph rank — 22,505 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@PPPJP · 3,255,955127 postsافتارات اغاني كروبات عاشكها
@PPPPJ · 2,362,428126 posts{ متحركات ملصقات GIF }
@KKKKB · 1,286,554124 postsاقتباسات ستوريات مَشـَاعر •
@YYYYD · 1,713,531124 postsلــ مَريمّ الغرابي 💜.
@lltkii · 3741 postمسلسل معاويه _ معاويه
@NU_VMBR · 9731 post؏ـمَّـار 🇵🇸
@oof24 · 3,9761 post
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
Named by 3 registered channels — 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.
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
@YYYXY 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 1 post, 8 August 2026 – 8 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“عبارات | ليطمئن قلبي” (@YYYXY), 1,085,698 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/YYYXY.
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.