Telegram RegisterThe public register of Telegram
Telegram profile photo for شام كاش Sham Cash - شروحات وحلول

Channel

شام كاش Sham Cash - شروحات وحلول

@shamcash01

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

771subscribers

-22 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002759682815
TypeChannel
Username@shamcash01
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/shamcash01

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 90% 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.

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 word for word on 1 other registered channel. They sit inside a group of 5 channels that share the same post bodies 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.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@shamcash01/135 · this entry19 May 2026, 19:47 UTC@wysytfg/12819 May 2026, 20:38 UTC1.0052 minutes
@wysytfg/1456 Jul 2026, 17:24 UTC@shamcash01/148 · this entry6 Jul 2026, 17:27 UTC1.003 minutes
@wysytfg/1511 Aug 2026, 22:19 UTC@shamcash01/152 · this entry2 Aug 2026, 04:36 UTC1.006.3 hours
@wysytfg/1522 Aug 2026, 20:08 UTC@shamcash01/153 · this entry3 Aug 2026, 05:39 UTC1.009.5 hours
@wysytfg/1382 Jun 2026, 18:38 UTC@shamcash01/137 · this entry2 Jun 2026, 18:39 UTC0.9872 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@wysytfg5 (5/5 hand-verifiable sample passed)1.0052 minutes@wysytfg (4–1)

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 4 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 13 comparable posts for this entry, running 17 May 2026 to 3 August 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).

Across the whole group of 5, the earliest publisher we hold is @shamcashapp. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 4 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

7567967766 August 2026 — 793 subscribers6 August 2026 — 793 subscribers7 August 2026 — 796 subscribers14 August 2026 — 769 subscribers22 August 2026 — 758 subscribers29 August 2026 — 756 subscribers6 September 2026 — 782 subscribers14 September 2026 — 771 subscribers7716 August 202614 September 2026
8 measurements spanning 39 days, net -22. 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 750–802 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 05:41771-11
6 Sept 2026, 13:40782+26
29 Aug 2026, 02:37756-2
22 Aug 2026, 22:23758-11
14 Aug 2026, 14:47769-27
7 Aug 2026, 04:52796+3
6 Aug 2026, 15:32793no change
6 Aug 2026, 09:21793first reading

Engagement

20 posts held, back to 8 May 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

134 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 45.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6145.5%
👍4835.8%
🥰118.21%
😍85.97%
👏53.73%
🔥10.746%

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 20 of the 20 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 134 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 8 May 2026 to 3 August 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

3 Aug 2026, 05:39 UTC190 views10 reactionsread 6 August 2026

#مؤقت السلام عليكم ورحمة الله وبركاته، عملاء شام كاش الكرام، بفضل الله، تمت إعادة تفعيل جميع خدمات الدفع، وعادت للعمل بشكل طبيعي. نشكر لكم صبركم وتفهمكم، ونعتذر عن أي إزعاج تسبب به هذا التوقف المؤقت.

👍7🥰3

2 Aug 2026, 04:36 UTC259 views6 reactionsread 6 August 2026

#مؤقت السلام عليكم ورحمة الله وبركاته، عملاء شام كاش الكرام، نعتذر عن توقف بعض خدمات الدفع عن طريق شام كاش بسبب وجود مشكلة في الربط الشبكي مع مزودي هذه الخدمات. يعمل فريقنا على معالجة المشكلة وإعادة خدمات الدفع المتوقفة إلى العمل في أسرع وقت ممكن بإذن الله. سوف نقوم بإعلامكم فور إعادة تفعيل الخدمات وعودتها للعمل. نشكر لكم تفهمكم وتعاونكم، ونعتذر عن أي إزعاج قد يترتب على ذلك.

👍5🥰1

12 Jul 2026, 13:09 UTC704 views10 reactionsread 6 August 2026

عرض خاص من #سيريتل ! فعّل باقة 5 غيغا لـ 30 يوم بس بـ 60 ل.س جديدة، واحصل على 100 دقيقة هدية مجاناً لمدة 3 أيام.

❤5👍4👏1

8 Jul 2026, 10:42 UTC890 views10 reactionsread 6 August 2026

عملاء "شام كاش" الأعزاء، يرجى منكم تعديل واستكمال بيانات حسابكم في "شام كاش"، بحيث تكون مطابقة تماماً للبيانات الواردة في البطاقة الشخصية أو إخراج القيد، ويمكنكم تنفيذ هذه الخطوة بسهولة من داخل التطبيق. ونذكّركم بأن استكمال بيانات الحساب ومطابقتها للبيانات الرسمية يُعد خطوة لازمة لضمان استمرار استخدام حسابكم بصورة طبيعية ومنتظمة. ولأي مساعدة أو إرشاد، يمكنكم التواصل مع فريق خدمة الزبائن عبر القنوات الرسمية "لشام ك…

❤5👍5

7 Jul 2026, 10:06 UTC889 views5 reactionsread 6 August 2026

عملاء "شام كاش" الأعزاء، نود تذكيركم بالتعامل بحذر مع أي عروض أو رسائل غير رسمية تطلب تحويل مبالغ مالية أو مشاركة بيانات الحساب، سواء كانت تحت عنوان قرض أو فرصة استثمار أو أرباح عبر الإنترنت أو مجموعات تسويق أو ادعاء تمثيل "شام كاش" لتوثيق الحساب أو تفعليه أو ترقيته. وتعتمد "شام كاش" في تواصلها معكم على قنواتها الرسمية فقط، ولا تطلب منكم مشاركة رمز التحقق OTP أو بيانات الحساب مع أي شخص. في حال تعرضتم لأي محاولة نصب…

❤3👍2

6 Jul 2026, 17:27 UTC756 views7 reactionsread 6 August 2026

#مؤقت السلام عليكم ورحمة الله وبركاته عملاء شام كاش الكرام، نحيطكم علماً بأن توقف الخدمات ناتج عن حدوث عطل طارئ لدى مزودي خدمات الانترنت ،جاري العمل من قبلهم لحل المشكلة وعودة الخدمات للعمل بأسرع وقت ممكن بإذن الله. نقدّر صبركم وتفهمكم.

👍4❤3

4 Jul 2026, 11:07 UTC787 views4 reactionsread 6 August 2026
Photo

Photo, posted without a caption

🥰2❤1👍1

3 Jul 2026, 06:41 UTC678 views4 reactionsread 6 August 2026
Photo

Photo, posted without a caption

👍2🥰2

2 Jul 2026, 11:13 UTC715 views2 reactionsread 6 August 2026
Photo

هام لعملاء "شام كاش" الكرام، انطلاقاً من التزام "شام كاش" بالتطوير المستمر، وتعزيز الامتثال للمتطلبات التنظيمية، والارتقاء بمستوى التكامل مع المنظومة المالية والمصرفية، نود إعلامكم بأنه سيتم خلال الفترة القادمة تطبيق مجموعة من الضوابط والمعايير التنظيمية الجديدة على عددٍ من خدمات "شام كاش". وتأتي هذه الخطوة انسجاماً مع توجهات مصرف سورية المركزي، وتواؤماً مع أفضل الممارسات والمعايير الدولية في مجال خدمات الدفع الإلك…

👍2

1 Jul 2026, 08:31 UTC848 views6 reactionsread 6 August 2026
Photo

https://t.me/ZAIN_Sy_0

👍2👏2🔥1🥰1

29 Jun 2026, 13:56 UTC661 views11 reactionsread 6 August 2026
Forwarded from @CivilAffairsSyFile

استجابةً لملاحظات الإخوة المواطنين وحرصاً على تقديم أفضل تجربة رقمية، أطلقت الإدارة العامة للشؤون المدنية تحديثاً جديداً لتطبيق "الشؤون المدنية". - يعالج الإصدار الجديد الملاحظات التقنية السابقة. #وزارة_الداخلية_السورية #الإدارة_العامة_للشؤون_المدنية

❤6👍4😍1

24 Jun 2026, 11:16 UTC909 views7 reactionsread 6 August 2026
Photo

مع "شام كاش" .. أنجز مدفوعاتك خلال ثوانٍ وبكل سهولة وأمان. كما يمكنكم تصفح الموقع الرسمي "لشام كاش" على الويب من خلال الرابط التالي:https://shamcash.sy/ar #شام_كاش #sham_cash #سهولة_وأمان

❤4👍2👏1

Showing the 12 most recent of 20 posts we hold for @shamcash01. 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.

Forward network

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.

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.

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 14 September 2026 — this entry's latest reading, not the date you are reading this.

“شام كاش Sham Cash - شروحات وحلول” (@shamcash01), 771 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/shamcash01.

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.