Telegram RegisterThe public register of Telegram
Telegram profile photo for شام كاش

Channel

شام كاش

@shamcashapp2

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Stars · Posts · Citations · Cite this entry

3,782subscribers

+2,672 since we began measuring on 25 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003528903142
TypeChannel
Username@shamcashapp2
CreatedBetween 1 December 2025 and 28 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live14 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/shamcashapp2

Topic

Other / unclassifiable — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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 5 other registered channels. This entry also sits inside a group of 8 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@shamcashapp2/11 · this entry7 Apr 2026, 15:03 UTC@Shamcashpp1/3627 Apr 2026, 21:07 UTC1.006.1 hours
@shamcashapp2/13 · this entry20 Apr 2026, 20:53 UTC@Shamcashpp1/36521 Apr 2026, 03:59 UTC1.007.1 hours
@shamcashapp2/20 · this entry19 May 2026, 19:44 UTC@Shamcashpp1/37021 May 2026, 22:34 UTC1.002 days
@shamcashapp2/22 · this entry2 Jun 2026, 18:52 UTC@Shamcashpp1/3712 Jun 2026, 20:58 UTC1.002.1 hours
@shamcashapp2/29 · this entry2 Aug 2026, 20:08 UTC@Shamcashpp1/3812 Aug 2026, 20:54 UTC1.0046 minutes
@shamcashapp2/18 · this entry2 May 2026, 21:35 UTC@Shamcashpp1/3674 May 2026, 03:49 UTC0.9630 hours
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
ChannelMatching postsText overlapTypical gapPublished first
@Shamcashpp19 (8/8 hand-verifiable sample passed)0.9818 hoursthis entry (9–0)
@wysytfg8 (8/8 hand-verifiable sample passed)1.0010 minutes@wysytfg (6–2)
@RRXOR8 (8/8 hand-verifiable sample passed)1.005 minuteseven
@shamcashapp6 (6/6 hand-verifiable sample passed)1.005 minutes@shamcashapp (6–0)
@shamcash015 (5/5 hand-verifiable sample passed)1.0013 minutesthis entry (3–2)

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 18 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 18 comparable posts for this entry, running 7 April 2026 to 25 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).

Of the group of 8 channels, the one whose matching posts we hold earliest is @shamcashapp. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · 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.

Channels linked by matching posts

This channel is in a group of 8 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

1,0983,7822,44025 August 2026 — 1,110 subscribers25 August 2026 — 1,110 subscribers26 August 2026 — 1,128 subscribers29 August 2026 — 1,133 subscribers1 September 2026 — 1,132 subscribers4 September 2026 — 1,130 subscribers10 September 2026 — 1,118 subscribers13 September 2026 — 1,116 subscribers18 September 2026 — 1,106 subscribers27 September 2026 — 1,098 subscribers5 October 2026 — 1,325 subscribers11 October 2026 — 2,118 subscribers14 October 2026 — 2,373 subscribers17 October 2026 — 2,466 subscribers20 October 2026 — 2,622 subscribers23 October 2026 — 2,691 subscribers26 October 2026 — 2,888 subscribers29 October 2026 — 2,953 subscribers31 October 2026 — 3,012 subscribers3 November 2026 — 3,041 subscribers6 November 2026 — 3,090 subscribers9 November 2026 — 3,165 subscribers14 November 2026 — 3,782 subscribers25 August 202614 November 2026
23 measurements spanning 81 days, net +2,672. 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 695–4,185 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
14 Nov 2026, 15:073,782+617
9 Nov 2026, 16:173,165+75
6 Nov 2026, 14:103,090+49
3 Nov 2026, 15:183,041+29
31 Oct 2026, 23:363,012+59
29 Oct 2026, 04:482,953+65
26 Oct 2026, 09:012,888+197
23 Oct 2026, 02:072,691+69
20 Oct 2026, 09:102,622+156
17 Oct 2026, 14:182,466+93
14 Oct 2026, 20:262,373+255
11 Oct 2026, 07:582,118+793
5 Oct 2026, 07:161,325+227
27 Sept 2026, 06:581,098-8
18 Sept 2026, 01:581,106-10
13 Sept 2026, 14:421,116-2
10 Sept 2026, 04:171,118-12
4 Sept 2026, 18:581,130-2
1 Sept 2026, 10:041,132-1
29 Aug 2026, 11:181,133first reading

Engagement

20 posts held, back to 28 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 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 25 August 2026. An engagement rate over an empty window would be a number about nothing.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 19 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @shamcashapp2. 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 28 March 2026 to 25 August 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

25 Aug 2026, 14:49 UTC872 viewsread 25 August 2026

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

13 Aug 2026, 19:02 UTC252 viewsread 25 August 2026

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

2 Aug 2026, 20:08 UTC450 viewsread 25 August 2026

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

1 Aug 2026, 22:30 UTC461 viewsread 25 August 2026

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

9 Jul 2026, 17:48 UTC703 viewsread 25 August 2026

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

8 Jul 2026, 10:48 UTC≈11,100 viewsread 25 August 2026

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

6 Jul 2026, 17:32 UTC≈12,500 viewsread 25 August 2026

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

5 Jul 2026, 08:35 UTC666 viewsread 25 August 2026

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

2 Jun 2026, 18:52 UTC≈12,100 viewsread 25 August 2026

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

25 May 2026, 20:28 UTC≈12,800 viewsread 25 August 2026

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

19 May 2026, 19:44 UTC≈1,580 viewsread 25 August 2026
Photo

السلام عليكم ورحمة الله وبركاته ارتقِ بخدماتك الرقمية إلى مستوى جديد مع واجهات برمجة التطبيقات (API) من شام كاش. الآن أصبح بإمكانك دمج خدمات شام كاش بسهولة مع متجرك الإلكتروني، تطبيقك، أو أي منظومة برمجية خاصة بك، لتوفير تجربة دفع واستقبال أموال سريعة، آمنة، وسلسة لعملائك. ابدأ بتفعيل التكامل البرمجي واطلب خدمة الـ API عبر الرابط: shamcash.sy/ar/apiRequest

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

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

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.

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

“شام كاش” (@shamcashapp2), 3,782 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/shamcashapp2.

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.