Telegram RegisterThe public register of Telegram

Channel

شروحات التطبيقات

@SSI_VPS

On this record: Growth · Engagement · Posts · Citations · Cite this entry

729subscribers

-2 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-1001269014656
TypeChannel
Username@SSI_VPS
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/SSI_VPS

Growth

7297317306 August 2026 — 731 subscribers6 August 2026 — 731 subscribers12 August 2026 — 729 subscribers6 August 202612 August 2026
3 measurements spanning 6 days, net -2. 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 729–731 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 16:08729-2
6 Aug 2026, 16:12731no change
6 Aug 2026, 05:50731first reading

Engagement

14 posts held, back to 1 February 2026the 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.

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

Recent posts

1 Jul 2026, 01:09 UTC49 viewsread 6 August 2026

https://www.facebook.com/share/v/1AnRKoc7bd/

Signed AbuHaider Shami

4 May 2026, 05:29 UTC129 viewsread 6 August 2026

https://www.facebook.com/share/r/17Z1VzpBcR/

Signed AbuHaider Shami

4 May 2026, 05:18 UTC122 viewsread 6 August 2026

https://www.facebook.com/share/v/1JJ9Shykge/

Signed AbuHaider Shami

27 Apr 2026, 01:20 UTC175 viewsread 6 August 2026

https://t.me/lemon_casher_bot/LEMONCASH/?startapp=r_e6zPivRq5KWDaUb Limon tıkla, görev yap ve gerçek para kazan 🤑 Kartına bir saat içinde ödeme 🚀

Signed AbuHaider Shami

18 Apr 2026, 22:36 UTC193 viewsread 6 August 2026

https://t.me/lemon_casher_bot/LEMONCASH/?startapp=r_e6zPivRq5KWDaUb Limon tıkla, görev yap ve gerçek para kazan 🤑 Kartına bir saat içinde ödeme 🚀

Signed AbuHaider Shami

1 Mar 2026, 01:15 UTC242 views0 reactionsread 6 August 2026

Bu benim referans bağlantım: https://www.paidwork.com/?r=mhmdnmr11

Signed AbuHaider Shami

11 Feb 2026, 05:21 UTC236 viewsread 6 August 2026

https://t.me/lemon_casher_bot/LEMONCASH/?startapp=r_e6zPivRq5KWDaUb Limon tıkla, görev yap ve gerçek para kazan 🤑 Kartına bir saat içinde ödeme 🚀

Signed AbuHaider Shami

7 Feb 2026, 10:35 UTC221 viewsread 6 August 2026

https://t.me/lemon_casher_bot/LEMONCASH/?startapp=r_e6zPivRq5KWDaUb Limon tıkla, görev yap ve gerçek para kazan 🤑 Kartına bir saat içinde ödeme 🚀

Signed AbuHaider Shami

6 Feb 2026, 02:11 UTC206 viewsread 6 August 2026

https://join.honeygain.com/LALNM94E41?achievement=onboarding

Signed AbuHaider Shami

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

Citation-graph rank

Citation-graph rank — 199,373 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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

“شروحات التطبيقات” (@SSI_VPS), 729 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SSI_VPS.

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.