Topic
Literature — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 17 November 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 9 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 6 comparable posts for this entry, running 4 November 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
- Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
- 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
- shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
- Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 9 channels, the one whose matching posts we hold earliest is @oaama51. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Channels linked by matching posts
This channel is in a group of 9 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
Growth
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
Engagement
20 posts held, back to 2 November 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 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 69.5%
- avg views ÷ 191 subscribers
- Avg views / post
- 133
- 20 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 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. It is computed over the 10 of 20 measured posts that carry a reaction reading, and over those same posts' views.
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
- 75
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 16 November 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.
Telegram Stars
- Stars received
- 32
- across the posts below
- Posts paid on
- 10
- of 20 we hold a reading for · 50%
- Most on one post
- 8
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @lima_a21. 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 20 most recent posts we hold for this entry, published 2 November 2026 to 16 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 5 of 20 posts held from the last 30 days (25.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
16 Nov 2026, 12:05 UTC379 views0 reactions3 Starsread 16 November 2026 Photo
مَازَالَ صَوْتُكَ فِي ثَنَايَا مَسْمَعِي
وَالشَّوْقُ فِي صَدْرِي يُفَتِّتُ أَضْلُعِي
وَاللَّهِ إِنَّ الشَّوْقَ فَاقَ تَحَمُّلِي
يَا شَوْقُ رِفْقًا بِالْفُؤَادِ أَلَا تَعِي؟
يَا زَهْرَتِي إِنْ مَرَّ اسْمُكِ عَابِرًا
يَزْدَادُ مِنْ فَرْطِ الْحَنِينِ تَوَجُّعِي
حَاوَلْتُ أَنْ أُخْفِيَ هَوَاكِ وَكُلَّمَا
أَخْفَيْتُهُ فِي الْقَلْبِ فَاضَتْ أَدْمُعِي.🌟
♡˚₊𐙚⋆
15 Nov 2026, 17:30 UTC38 viewsread 16 November 2026 ـــــ
14 Nov 2026, 22:19 UTC61 views0 reactions2 Starsread 16 November 2026 Photo
أويتُ إليكَ من عَناءٍ لم تُدركهُ،
فكان عَتَبُكَ أوجعَ من عَناءِ فراري.🦋
♡˚₊𐙚⋆
14 Nov 2026, 22:19 UTC58 viewsread 16 November 2026 ــــــ
14 Nov 2026, 15:05 UTC67 viewsread 16 November 2026 ---*
Signed 𝓡𝓪𝔂𝓱𝓪𝓷𝓪♡˚₊𐙚⋆
13 Nov 2026, 09:05 UTC109 views0 reactions3 Starsread 16 November 2026 Photo
لِماذا أعودُ إليكَ لأشقى؟
إذا الحُبُّ ضاعَ فماذا تبقّى؟
أمِنْ أجلِ عهدِ هوانا القديمِ
أُصادِقُ عصفًا ورعدًا وبرقًا؟
إذا ما نسيتُ الذي قد لقيتُ
فكيفَ سأنسى الذي سوفَ ألقى؟
وماذا لديكَ سوى القيدِ قُلْ لي
وهل بقيودِكَ أسمو وأرقى؟
أعودُ لأمنحَ عينيكَ أمنًا
فليتَكَ تمنحُ للقلبِ خفقًا
وليتَكَ تفهمُ معنى رجوعي
إليكَ بجرحٍ سيزدادُ عمقًا🌹.
♡˚₊𐙚⋆
13 Nov 2026, 09:04 UTC84 viewsread 16 November 2026 ـــــ
12 Nov 2026, 00:33 UTC121 views0 reactions8 Starsread 16 November 2026 Photo
“اللهمّ إن كان قلبي قد اختاره سرًّا… فاختره لي جهرًا، وبلّغني إيّاه بلطفك.”⭐
♡˚₊𐙚⋆
10 Nov 2026, 23:13 UTC120 viewsread 16 November 2026 ـــــــ
10 Nov 2026, 16:56 UTC119 views0 reactions3 Starsread 16 November 2026 Photo
أُداويكَ من وجعِ الحياةِ بقُربِنا
ويُبرئني منك الحضورُ إذا دنا
فما عادَ وجعُكَ في فؤادِكَ وحدَهُ
ولا عادَ جرحي دونَ قربِكَ يُحتوى
كأنّا خُلِقنا في الهوى متعانقَيْنِ
فأنتَ شفاءُ الروحِ، وأنا لكَ السَّكَنُ. ❤️
♡˚₊𐙚⋆
10 Nov 2026, 16:56 UTC106 viewsread 16 November 2026 ـــــــ
9 Nov 2026, 00:24 UTC121 views0 reactions2 Starsread 16 November 2026 Photo
كان عليك أن تغادر منذ انقباضة صدرك الأولى..... لكنك غامرت.🖤
♡˚₊𐙚⋆
Showing the 12 most recent of 20 posts we hold for @lima_a21. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
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 16 November 2026 — this
entry's latest reading, not the date you are reading this.
“لِمًَ ؟” (@lima_a21), 191 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/lima_a21.
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.