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

Channel
@Shamcashpp1
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,170subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001765099168 |
|---|---|
| Type | Channel |
| Username | @Shamcashpp1 |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Shamcashpp1 |
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 73% 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.
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 word for word on 3 other registered channels. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @shamcashapp/1217 Apr 2026, 15:02 UTC | @Shamcashpp1/362 · this entry7 Apr 2026, 21:07 UTC | 1.00 | 6.1 hours |
| @shamcashapp/13619 May 2026, 19:41 UTC | @Shamcashpp1/370 · this entry21 May 2026, 22:34 UTC | 1.00 | 2 days |
| @shamcashapp/1448 Jul 2026, 10:37 UTC | @Shamcashpp1/378 · this entry9 Jul 2026, 04:44 UTC | 1.00 | 18 hours |
| @shamcashapp/1492 Aug 2026, 20:07 UTC | @Shamcashpp1/381 · this entry2 Aug 2026, 20:54 UTC | 1.00 | 47 minutes |
| @shamcashapp/1312 May 2026, 21:31 UTC | @Shamcashpp1/367 · this entry4 May 2026, 03:49 UTC | 0.96 | 30 hours |
| @shamcashapp/1459 Jul 2026, 17:26 UTC | @Shamcashpp1/380 · this entry10 Jul 2026, 20:34 UTC | 0.94 | 27 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @shamcashapp | 9 (8/8 hand-verifiable sample passed) | 0.97 | 27 hours | @shamcashapp (9–0) |
| @wysytfg | 6 (6/6 hand-verifiable sample passed) | 0.98 | 23 hours | @wysytfg (6–0) |
| @RRXOR | 5 (5/5 hand-verifiable sample passed) | 0.98 | 27 hours | @RRXOR (5–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 20 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 16 comparable posts for this entry, running 9 March 2026 to 2 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.
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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 02:16 | 1,170 | -1 |
| 10 Aug 2026, 20:27 | 1,171 | +1 |
| 7 Aug 2026, 23:33 | 1,170 | no change |
| 7 Aug 2026, 17:37 | 1,170 | first reading |
20 posts held, back to 9 March 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 pageof 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.
| Window | Rolling 30 days · latest post in window 2 August 2026 |
|---|---|
| Posts held | 20 (9 March 2026 – 2 August 2026) |
| Views total | 341 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:33 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.
137 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 79.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 109 | 79.6% | |
| 👍 | 12 | 8.76% | |
| 🤔 | 8 | 5.84% | |
| 🔥 | 3 | 2.19% | |
| 🥰 | 3 | 2.19% | |
| 😡 | 2 | 1.46% |
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 137reactions 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 9 March 2026 to 2 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.
#مؤقت السلام عليكم ورحمة الله وبركاته، عملاء شام كاش الكرام، بفضل الله، تمت إعادة تفعيل جميع خدمات الدفع، وعادت للعمل بشكل طبيعي. نشكر لكم صبركم وتفهمكم، ونعتذر عن أي إزعاج تسبب به هذا التوقف المؤقت.
❤5😡2
عملاء شام كاش الأعزاء يرجى منكم تعديل واستكمال بيانات حسابكم في شام كاش، بحيث تكون مطابقة تماماً للبيانات الواردة في البطاقة الشخصية أو إخراج القيد، ويمكنكم تنفيذ هذه الخطوة بسهولة من داخل التطبيق. ونذكّركم بأن استكمال بيانات الحساب ومطابقتها للبيانات الرسمية يُعد خطوة لازمة لضمان استمرار استخدام حسابكم بصورة طبيعية ومنتظمة. ولأي مساعدة أو إرشاد، يمكنكم التواصل مع فريق خدمة الزبائن عبر القنوات الرسمية لشام كاش. h…
❤7
عملاء شام كاش الأعزاء نود تذكيركم بالتعامل بحذر مع أي عروض أو رسائل غير رسمية تطلب تحويل مبالغ مالية أو مشاركة بيانات الحساب، سواء كانت تحت عنوان قرض أو فرصة استثمار أو أرباح عبر الإنترنت أو مجموعات تسويق أو ادعاء تمثيل شام كاش لتوثيق الحساب أو تفعليه أو ترقيته. وتعتمد شام كاش في تواصلها معكم على قنواتها الرسمية فقط، ولا تطلب منكم مشاركة رمز التحقق OTP أو بيانات الحساب مع أي شخص. في حال تعرضتم لأي محاولة نصب أو احت…
❤8
#مؤقت السلام عليكم ورحمة الله وبركاته عملاء شام كاش الكرام، نحيطكم علماً بأن توقف الخدمات ناتج عن حدوث عطل طارئ لدى مزودي خدمات الانترنت ،جاري العمل من قبلهم لحل المشكلة وعودة الخدمات للعمل بأسرع وقت ممكن بإذن الله. نقدّر صبركم وتفهمكم. https://t.me/Shamcashpp1
❤9
مستخدمي شام كاش الأكارم، تواصل شام كاش تطوير خدماتها بما يواكب أفضل الممارسات التنظيمية، ويعزز جودة الخدمة وأمانها واستقرارها، انسجاماً مع التوجهات التنظيمية لمصرف سورية المركزي والمعايير الدولية ذات الصلة. ورسالتنا كما كانت دائماً: تقديم حلول دفع وتحويل سهلة وسريعة وآمنة، مع المحافظة على تجربة استخدام مرنة وموثوقة. وسيتم الإعلان عن أي تحديثات أو مستجدات تتعلق بخدماتنا بكل وضوح عبر منصاتنا الرسمية، حرصاً على إبقاء…
❤3
Photo, posted without a caption
❤6
🔴 إدارة تطبيق "شام كاش": سيتم خلال الفترة القادمة تطبيق مجموعة من الضوابط والمعايير التنظيمية الجديدة على عدد من خدمات "شام كاش"، وذلك انسجاماً مع توجهات مصرف سورية المركزي وتوافقاً مع أفضل الممارسات والمعايير الدولية في مجال خدمات الدفع الإلكتروني، بما يسهم في تعزيز مستويات الامتثال والحوكمة، والارتقاء بجودة الخدمات. https://t.me/Shamcashpp1
❤9
قال مدير قسم #التسويق والعلاقات العامة في " #شام_كاش " محمد بسيكي، إن الشركة بدأت استقبال طلبات الربط البرمجي (API) من الشركات والتطبيقات المختلفة عبر رابط خاص للتسجيل، بهدف تمكين #الدفع_الإلكتروني وتوسيع التكامل الرقمي بين المنصات. وأضاف أن إدراج أي خدمة جديدة يعتمد على استكمال التنسيق والربط مع الجهة المعنية، مؤكداً انفتاح الشركة الكامل على التعاون مع جميع الجهات العامة والخاصة. وأشار إلى أن الشركة تعمل حالياً عل…
❤7
#مؤقت السلام عليكم ورحمة الله وبركاته، عملاء شام كاش الكرام، نود إعلامكم بأنه سيتم إيقاف خدمات التطبيق مؤقتاً اعتباراً من الساعة 12:00 منتصف الليل لإجراء أعمال صيانة وتحديث على الشبكة والبنية التحتية. ستعود الخدمات فور الانتهاء من الأعمال الفنية والتأكد من جاهزيتها. نعتذر عن أي إزعاج، ونشكركم على تفهمكم وتعاونكم.
❤5🤔1
السلام عليكم ورحمة الله وبركاته ارتقِ بخدماتك الرقمية إلى مستوى جديد مع واجهات برمجة التطبيقات (API) من شام كاش. الآن أصبح بإمكانك دمج خدمات شام كاش بسهولة مع متجرك الإلكتروني، تطبيقك، أو أي منظومة برمجية خاصة بك، لتوفير تجربة دفع واستقبال أموال سريعة، آمنة، وسلسة لعملائك. ابدأ بتفعيل التكامل البرمجي واطلب خدمة الـ API عبر الرابط: shamcash.sy/ar/apiRequest
❤4🤔4
أكد مدير التسويق والعلاقات العامة في تطبيق #شام_كاش محمد بسيكي، أن التطبيق يواصل توسيع خدماته المالية والإلكترونية في مختلف المحافظات السورية، موضحاً أن عدد المستخدمين تجاوز 4 ملايين و200 ألف مستخدم، مع تنفيذ نحو مليوني عملية تحويل يومياً، في ظل تزايد الاعتماد على #الدفع_الرقمي و #الخدمات_الإلكترونية. وأوضح أن التطبيق يتيح خدمات التحويل المالي والدفع الإلكتروني وتسديد الفواتير والرسوم الحكومية، إلى جانب خدمات مرتبط…
❤4
بعض الانقطاعات المؤقتة قد تحدث في الخدمات خلال الفترة الحالية بسبب أعمال تطوير في البنية التحتية
👍2
Showing the 12 most recent of 20 posts we hold for @Shamcashpp1. 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Sham Cash” (@Shamcashpp1), 1,170 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Shamcashpp1.
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.