Channel
@Srylove
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Stars · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
288,698subscribers
+61,901 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001329403113 |
|---|---|
| Type | Channel |
| Username | @Srylove |
| Description | یک سوم حجم بدنم از حرفایی که ریختم تو خودم تشکیل شده. |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 57 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/Srylove |
Personal blog — 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 96% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Listenwithmeif | 7 (7/7 hand-verifiable sample passed) | 1.00 | 6.7 hours | this entry (7–0) |
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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 110 comparable posts for this entry, running 4 August 2026 to 10 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @Srylove — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 09:31 | 288,698 | +1,027 |
| 9 Nov 2026, 00:57 | 287,671 | +1,317 |
| 7 Nov 2026, 16:07 | 286,354 | +1,478 |
| 6 Nov 2026, 14:46 | 284,876 | -1,025 |
| 5 Nov 2026, 13:45 | 285,901 | +1,730 |
| 4 Nov 2026, 11:54 | 284,171 | +2,067 |
| 3 Nov 2026, 09:38 | 282,104 | +1,607 |
| 2 Nov 2026, 09:55 | 280,497 | +280,475 |
| 25 Oct 2026, 23:36 | 22 | -270,982 |
| 24 Oct 2026, 23:45 | 271,004 | +883 |
| 23 Oct 2026, 23:17 | 270,121 | +431 |
| 22 Oct 2026, 22:47 | 269,690 | -882 |
| 21 Oct 2026, 18:29 | 270,572 | -844 |
| 20 Oct 2026, 11:17 | 271,416 | +1,281 |
| 19 Oct 2026, 09:16 | 270,135 | -608 |
| 18 Oct 2026, 06:49 | 270,743 | +1,246 |
| 17 Oct 2026, 09:39 | 269,497 | +2,711 |
| 16 Oct 2026, 11:19 | 266,786 | -773 |
| 15 Oct 2026, 14:40 | 267,559 | -870 |
| 14 Oct 2026, 14:38 | 268,429 | first reading |
767 posts held, back to 4 August 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 204 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. It is computed over the 42 of 173 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 767 (4 August 2026 – 10 November 2026) |
| Views total | 10,335,564 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 02:58 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.
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Srylove. 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 767 most recent posts we hold for this entry, published 4 August 2026 to 10 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.
Telegram’s own ‘edited’ marker: 0 of 173 posts held from the last 30 days (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).
تو فکر کردی با چند تا دروغ میتونی حقیقت رو برای همیشه پنهون کنی؛ مشکل اینجاست که من خیلی زودتر از چیزی که فکر میکردی فهمیدم، فقط منتظر بودم ببینم تا کجا میخوای نقش بازی کنی. دروغ گفتی، بعد انکار کردی، بعد برای انکارت هم داستان ساختی؛ انگار هر دروغ جدید قراره قبلی رو نجات بده. من از دروغهات ناراحت نشدم؛ از این خندم گرفت که برای صادق به نظر رسیدن، اینهمه زحمت کشیدی و آخرش باز خودت رو لو دادی. - Shadow
Signed Shadow
چه اشتباهی کردم، حرفاتو باور کردم. @SryLove
Signed Aria
فدای سرت؛ خیلی عبارت زیبا و گرمیه و انگار با بیانش داری به فرد اطمینان میدی که تو مهم تر از یه اشتباه هستی.
Signed Aria
در این جهان به دنبال همه چیز بگرد ؛ بجز عشق و مرگ،آنها تو را در زمان درست پیدا خواهند کرد.
Signed Aria
ته ته هول بازی و خیانت و دوستی های معتدتون،یه روح خسته و سردرگم میمونه براتون که حتی به خودتون هم تعلق نداره،نجیب زندگی کنید و قلب روحتون رو ارزون نفروشید.
Signed Aria
رها کن عزیزم؛ تو از سرشم زیاد بودی اون توی رویاهاشم نمیتونست با های کپی تو باشه چه برسه به هم لول تو.
Signed Aria
حالا کاری ندارم؛ ولی آدم مورد علاقتون درس عبرت نشده براتون که بدونید دنیا چه جای مزخرفیه.
Signed Aria
۶ نفرررر
۸ نفرررر موندددد
به خاطر نامزدی ادمین ( سارای عزیز ) لینک کانال VIP رو برای 5 دقیقه میزارم بعد پاک میکنم 🤍 : @VIPChnl
پاک کنممم ؟
۱ نفررررر اخررررر
Showing the 12 most recent of 767 posts we hold for @Srylove. 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.
We recorded 63 posts on @Srylove as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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.
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.
@Srylove 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.
References a handle that is not a live channel — we have no record it ever was one.
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 August 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 24 seed channels' Telegram-generated recommendation lists in total. 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“𝙞'𝙢 𝙎𝙤𝙧𝙧𝙮” (@Srylove), 288,698 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/Srylove.
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.