Marketing & affiliate — 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 39% 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. 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.
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
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. 9 of the 9 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 1,380 comparable posts for this entry, running 7 August 2026 to 11 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).
Recorded under the keys clone_copy · clone_mutual, 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.
Growth
62 measurements spanning 94 days, net +6,133. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 15,026–23,009 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)
Subscribers
Change
9 Nov 2026, 19:28
22,088
+490
8 Nov 2026, 10:47
21,598
-75
7 Nov 2026, 02:08
21,673
-47
6 Nov 2026, 00:44
21,720
-197
5 Nov 2026, 03:20
21,917
+52
4 Nov 2026, 00:25
21,865
-71
3 Nov 2026, 03:49
21,936
+56
2 Nov 2026, 06:34
21,880
+31
1 Nov 2026, 08:38
21,849
+73
31 Oct 2026, 10:58
21,776
+27
30 Oct 2026, 12:44
21,749
+78
29 Oct 2026, 12:56
21,671
+65
28 Oct 2026, 08:57
21,606
+23
27 Oct 2026, 07:27
21,583
+77
26 Oct 2026, 08:30
21,506
+33
25 Oct 2026, 06:34
21,473
+162
24 Oct 2026, 03:28
21,311
-25
23 Oct 2026, 02:28
21,336
+26
22 Oct 2026, 00:35
21,310
+292
20 Oct 2026, 17:47
21,018
first reading
Engagement
1,384 posts held, back to 7 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 70 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.104%
avg views ÷ 22,088 subscribers
Avg views / post
23.1
324 posts measured
Reaction rate
5.50%
reactions ÷ views · ER floor
Posts in window
324
of 1,384 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 9 of 324 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 11 November 2026
Posts held
1,384 (7 August 2026 – 11 November 2026)
Views total
7,475
Reactions total
12
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 03:09 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
≈8
Links
≈53,500
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.
Reaction mix
37 reactions across 31 posts, in 10 distinct kinds. The most used accounts for 54.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
20
54.1%
🔥
7
18.9%
💋
2
5.41%
💩
2
5.41%
❤🔥
1
2.70%
👌
1
2.70%
💯
1
2.70%
🤣
1
2.70%
🤩
1
2.70%
🥰
1
2.70%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 31 of the 1,000 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 37 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 15 August 2026 to 11 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Telegram’s own ‘edited’ marker: 1 of 324 posts held from the last 30 days (0.309%) 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).
تم اكتمال تمويل القناه! 🎉
القناة: ليت موشن وفيدو ستار
عدد الأعضاء الي تم تمويلهم: 58
رابط القناه:
https://t.me/hdjdbihfg
شكرًا لثقتكم في بوت الغراب♥️ .
تم اكتمال تمويل القناه! 🎉
القناة: قناة الصـبيـحاوي 🥷🖤
عدد الأعضاء الي تم تمويلهم: 20
رابط القناه:
https://t.me/grcpro
شكرًا لثقتكم في بوت الغراب♥️ .
تم اكتمال تمويل القناه! 🎉
القناة: Канал Кобар
عدد الأعضاء الي تم تمويلهم: 10
رابط القناه:
https://t.me/mim5w6
شكرًا لثقتكم في بوت الغراب♥️ STTARTBOT.
تم اكتمال تمويل القناه! 🎉
القناة: ابـن النـاصريـة
عدد الأعضاء الي تم تمويلهم: 10
رابط القناه:
https://t.me/alnasery01
شكرًا لثقتكم في بوت الغراب♥️ .
تم اكتمال تمويل القناه! 🎉
القناة: كروب دردشات تعارف سوريا
عدد الأعضاء الي تم تمويلهم: 25
رابط القناه:
https://t.me/mh_sy_97_mh
شكرًا لثقتكم في بوت الغراب♥️ .
تم اكتمال تمويل القناه! 🎉
القناة: قناة:ســّر ᷂ﺄلحــــيّاة⇣
عدد الأعضاء الي تم تمويلهم: 18
رابط القناه:
https://t.me/sjdoow
شكرًا لثقتكم في بوت الغراب♥️ .
تم اكتمال تمويل القناه! 🎉
القناة: وكاله تعليق الدراسة
عدد الأعضاء الي تم تمويلهم: 12
رابط القناه:
https://t.me/nllnlio
شكرًا لثقتكم في بوت الغراب♥️ .
تم اكتمال تمويل القناه! 🎉
القناة: منصة شام للوظائف والاعلانات
عدد الأعضاء الي تم تمويلهم: 10
رابط القناه:
https://t.me/sham20012
شكرًا لثقتكم في بوت الغراب♥️ .
تم اكتمال تمويل القناه! 🎉
القناة: ءل مـشـࢪحـة^^
عدد الأعضاء الي تم تمويلهم: 25
رابط القناه:
https://t.me/xxxx_al
شكرًا لثقتكم في بوت الغراب♥️ .
Showing the 12 most recent of 1,384 posts we hold for @srwrtt. 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.
Handles this channel named that no longer answer
Dead references
76
handles named in this channel’s posts, vacant today
Evidenced gone
67
we ourselves saw one of these resolve, at some point
Never seen alive
9
vacant every time we have ever looked
@srwrtt named 76 handles 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@it_9ri named in 3 posts, 3 September 2026 – 3 September 2026 · confirmed gone 6 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@hjj_71 named in 2 posts, 3 September 2026 – 3 September 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@huda212000 named in 2 posts, 8 August 2026 – 27 August 2026 · confirmed gone 9 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@arwa71288 named in 2 posts, 16 August 2026 – 27 August 2026 · confirmed gone 18 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@aassqwwwz named in 2 posts, 25 August 2026 – 27 August 2026 · confirmed gone 2 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@vwvw1ll named in 2 posts, 9 August 2026 – 16 August 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@abob200 named in 2 posts, 15 August 2026 – 15 August 2026 · confirmed gone 12 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@fshbkn named in 2 posts, 11 August 2026 – 15 August 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@yamenerrrrrr named in 2 posts, 8 August 2026 – 11 August 2026 · confirmed gone 31 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@l_ildy named in 2 posts, 9 August 2026 – 11 August 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@g1hfran named in 2 posts, 9 August 2026 – 9 August 2026 · confirmed gone 21 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@ghghftftf named in 1 post, 10 November 2026 – 10 November 2026 · confirmed gone 10 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@hiyhyi named in 1 post, 9 November 2026 – 9 November 2026 · confirmed gone 9 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@ttresas named in 1 post, 5 November 2026 – 5 November 2026 · confirmed gone 5 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@ellmz1 named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 5 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@reuu3i named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@djfjcjc666 named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@naathla_engineer named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 19 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@nemotop1 named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@ononnr named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@owr_r named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@r_24oa named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@r_e_k_o1 named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 7 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@footballsoccer902 named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 20 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@hcnb_313 named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 10 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@teba2007127 named in 1 post, 29 August 2026 – 29 August 2026 · confirmed gone 30 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@mrmnina named in 1 post, 29 August 2026 – 29 August 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@s2s_120 named in 1 post, 28 August 2026 – 28 August 2026 · confirmed gone 6 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@yahpnk named in 1 post, 28 August 2026 – 28 August 2026 · confirmed gone 5 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@xixixli3 named in 1 post, 27 August 2026 – 27 August 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@tawakal_3 named in 1 post, 27 August 2026 – 27 August 2026 · confirmed gone 9 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@yeuehhehekieoeosks named in 1 post, 27 August 2026 – 27 August 2026 · confirmed gone 19 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@hahraa123 named in 1 post, 25 August 2026 – 25 August 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@egy_ds named in 1 post, 25 August 2026 – 25 August 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@rb_rz1 named in 1 post, 25 August 2026 – 25 August 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@mkmompmp named in 1 post, 25 August 2026 – 25 August 2026 · confirmed gone 1 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@mmo2315 named in 1 post, 25 August 2026 – 25 August 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@msahus122 named in 1 post, 25 August 2026 – 25 August 2026 · confirmed gone 5 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@brazilyalhakem named in 1 post, 25 August 2026 – 25 August 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@gi_ma2 named in 1 post, 25 August 2026 – 25 August 2026 · confirmed gone 8 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@rdni27 named in 1 post, 16 August 2026 – 16 August 2026 · confirmed gone 31 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@igcxhi named in 1 post, 16 August 2026 – 16 August 2026 · confirmed gone 19 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@l1llic named in 1 post, 15 August 2026 – 15 August 2026 · confirmed gone 26 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@loveajk6 named in 1 post, 15 August 2026 – 15 August 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@m_lllyi named in 1 post, 11 August 2026 – 11 August 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@rraa15i named in 1 post, 11 August 2026 – 11 August 2026 · confirmed gone 26 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@lyi_1i named in 1 post, 11 August 2026 – 11 August 2026 · confirmed gone 27 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@nemo_m2 named in 1 post, 11 August 2026 – 11 August 2026 · confirmed gone 1 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@s3_lii named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@wherewhimsyspreads named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
26 more handles are in this same list but not shown individually here — capped at 50.
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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“اكتملات بوت تمويل الغراب🇾🇪⚡️” (@srwrtt), 22,088 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/srwrtt.
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.