Telegram RegisterThe public register of Telegram
Telegram profile photo for • [ ﷽ 𝗦𝗼𝘂𝗿𝗰𝗲𝘀 64𝗯𝗶𝘁 × 32𝗯𝗶𝘁 ] • قناة. سورسات ببجي

Channel

• [ ﷽ 𝗦𝗼𝘂𝗿𝗰𝗲𝘀 64𝗯𝗶𝘁 × 32𝗯𝗶𝘁 ] • قناة. سورسات ببجي

@Source_SsS

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

8,544subscribers

-125 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001717636201
TypeChannel
Username@Source_SsS
Description﴿‏ وَلسّوفَ يُعطِيكَ ربُّكَ فَتَرضَى ۗ ۝ ﴾ #قناة سورسات #قناة سورسات #قناة سورسات ﴿لَّن يُصِيبَنَا إِلَّا مَا كَتَبَ اللَّهُ لَنَا﴾.
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/Source_SsS

Topic

Gaming — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.

Growth

8,5418,6708,605.57 August 2026 — 8,669 subscribers7 August 2026 — 8,669 subscribers8 August 2026 — 8,670 subscribers11 August 2026 — 8,655 subscribers14 August 2026 — 8,647 subscribers17 August 2026 — 8,634 subscribers20 August 2026 — 8,629 subscribers24 August 2026 — 8,626 subscribers27 August 2026 — 8,622 subscribers30 August 2026 — 8,616 subscribers1 September 2026 — 8,605 subscribers5 September 2026 — 8,604 subscribers10 September 2026 — 8,581 subscribers14 September 2026 — 8,585 subscribers18 September 2026 — 8,579 subscribers27 September 2026 — 8,565 subscribers5 October 2026 — 8,541 subscribers12 October 2026 — 8,542 subscribers15 October 2026 — 8,546 subscribers19 October 2026 — 8,552 subscribers22 October 2026 — 8,543 subscribers25 October 2026 — 8,551 subscribers28 October 2026 — 8,552 subscribers30 October 2026 — 8,556 subscribers2 November 2026 — 8,551 subscribers5 November 2026 — 8,544 subscribers8,5447 August 20265 November 2026
26 measurements spanning 90 days, net -125. 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 8,522–8,689 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
5 Nov 2026, 10:018,544-7
2 Nov 2026, 19:078,551-5
30 Oct 2026, 20:468,556+4
28 Oct 2026, 04:508,552+1
25 Oct 2026, 03:168,551+8
22 Oct 2026, 04:588,543-9
19 Oct 2026, 00:598,552+6
15 Oct 2026, 22:588,546+4
12 Oct 2026, 17:578,542+1
5 Oct 2026, 17:558,541-24
27 Sept 2026, 18:028,565-14
18 Sept 2026, 15:208,579-6
14 Sept 2026, 16:578,585+4
10 Sept 2026, 17:378,581-23
5 Sept 2026, 21:558,604-1
1 Sept 2026, 23:258,605-11
30 Aug 2026, 07:178,616-6
27 Aug 2026, 13:448,622-4
24 Aug 2026, 08:128,626-3
20 Aug 2026, 15:568,629first reading

Engagement

91 posts held, back to 17 July 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 33 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.92%
avg views ÷ 8,544 subscribers
Avg views / post
848
22 posts measured
Reaction rate
0.328%
reactions ÷ views · ER floor
Posts in window
22
of 91 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 15 of 22 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 November 2026
Posts held91 (17 July 2026 – 5 November 2026)
Views total18,650
Reactions total42
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 10:22 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
≈7,050
Videos
≈1,950
Links
≈4,860

Lifetime counters from Telegram’s own channel header, read 5 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.

Video runtime
14m 16s
Average length
1m 18s

Measured directly from 11 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

273 reactions across 58 posts, in 18 distinct kinds. The most used accounts for 42.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣11642.5%
❤3813.9%
👍2810.3%
👎186.59%
🤡176.23%
😁145.13%
🤮145.13%
😱82.93%
👏41.47%
❤‍🔥31.10%
🌭31.10%
🤬31.10%
🍓20.733%
🌚10.366%
👌10.366%
👨‍💻10.366%
💯10.366%
🔥10.366%

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

Measured over the 91 most recent posts we hold, published 17 July 2026 to 5 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: 5 of 22 posts held from the last 30 days (22.7%) 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).

5 Nov 2026, 01:22 UTC281 views2 reactionsread 5 November 2026

وها صدك المطور حسد واحد عراق وعالم راح ينطيني قتل للنسخة خاف بعدين يكلي اني مسويلك ياها لان هذا بجيح ابن بجيح

❤2

Signed SajadAli

5 Nov 2026, 01:21 UTC282 views1 reactionsread 5 November 2026

اما عالنسخة واللودر وتطبيق الروت حسب ماسمعت السيزن باقيله كم يوم ف ننتظر ونشوف

❤1

Signed SajadAli

5 Nov 2026, 01:21 UTC293 views1 reactionsread 5 November 2026
Photo

سورس دزالي يا مصيول احدثه اله السورس ربه رافس السوك ماعنده خصيان مادري شعجبه بي

🤣1

Signed SajadAli

3 Nov 2026, 18:14 UTC602 views8 reactionsread 5 November 2026
Photo

Photo, posted without a caption

😱6❤2

Signed SajadAli

1 Nov 2026, 22:57 UTC862 viewsread 5 November 2026

عاشق الببسي 😂 اه فدوه كافي سجاد العنيففف 😂 صورة عيري مع عشاق الببسي 😂

Signed SajadAli

1 Nov 2026, 22:56 UTC807 views1 reactionsread 5 November 2026
Forwarded from @g7czc

https://youtu.be/fTH8iF85D44?si=ly7a565iQRsyXPOo

❤1

Signed blَack

1 Nov 2026, 22:54 UTC797 viewsread 5 November 2026
Voice message

Voice message, posted without a caption

Signed SajadAli

1 Nov 2026, 22:51 UTC765 viewsread 5 November 2026

والله مادري شينيج بنفسه ذن فضايح مادري محادثات ماادري حجي

Signed SajadAli

1 Nov 2026, 22:50 UTC744 viewsread 5 November 2026

هاي فضايحي مثل مايكولون شباب

Signed SajadAli

31 Oct 2026, 21:10 UTC969 views1 reactionsread 5 November 2026

وهسه جايني واحد طلي سجاد انته شنو تعرف باللوا مال ملفات 🤣

🤣1

Signed SajadAli

31 Oct 2026, 21:10 UTC942 views3 reactionsread 5 November 2026

اني ما احجي بس على شغلة وحدة سكربت بدون تشفير بذاك الوكت و300kb (بدون تشفير)

🤣2😁1

Signed SajadAli

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

Posts edited after publishing

@Source_SsS edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
12 August 2026
Most recent edit
12 August 2026

Posts recorded as deleted after publishing

We recorded 5 posts on @Source_SsS 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.

First seen missing
10 August 2026
Most recent seen missing
18 August 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
0

Forward network

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

“• [ ﷽ 𝗦𝗼𝘂𝗿𝗰𝗲𝘀 64𝗯𝗶𝘁 × 32𝗯𝗶𝘁 ] • قناة. سورسات ببجي” (@Source_SsS), 8,544 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Source_SsS.

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.