Telegram RegisterThe public register of Telegram
Telegram profile photo for ՏHAƦK TƦADING

Channel

ՏHAƦK TƦADING

@SharkTrading

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

2,254subscribers

-27 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001369088348
TypeChannel
Username@SharkTrading
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live22 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/SharkTrading

Growth

2,2542,2812,267.56 August 2026 — 2,281 subscribers6 August 2026 — 2,281 subscribers9 August 2026 — 2,276 subscribers12 August 2026 — 2,275 subscribers15 August 2026 — 2,272 subscribers18 August 2026 — 2,260 subscribers22 August 2026 — 2,254 subscribers6 August 202622 August 2026
7 measurements spanning 16 days, net -27. 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 2,250–2,285 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 10:462,254-6
18 Aug 2026, 19:462,260-12
15 Aug 2026, 10:142,272-3
12 Aug 2026, 05:232,275-1
9 Aug 2026, 16:042,276-5
6 Aug 2026, 14:302,281no change
6 Aug 2026, 14:292,281first reading

Engagement

18 posts held, back to 11 July 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 18 posts for this entry, the most recent from 5 October 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Oct 2025, 09:49 UTC843 viewsread 7 August 2026

عندما بدأت التداول، كنت أُلقي باللوم على السوق في كل خسارة. 📉 صفقات سيئة؟ "تلاعب في السوق." 💸 أرباح فاتتني؟ "تقلبات غير عادلة." لكن في يومٍ ما أدركت — السوق لم يكن عدوي. عدوي الحقيقي كان مشاعري، 😤 نفاد صبري، 😣 وافتقاري للانضباط. 🧘‍♂️ المعركة الحقيقية لم تكن على الرسوم البيانية 📊 بل كانت في داخلي. 🧠 ليست المسألة *أنت ضد السوق*، بل *أنت ضد نفسك*. ⚔️🔥

18 Sept 2025, 09:55 UTC735 viewsread 7 August 2026
Forwarded from @TRADAMIND

خلال الدورة السابقة ..و بالضبط خلال الصعود .. كانت الناس تشتري اراضي من خلال metavers ..و الاسعار 🚀🚀 .. و اخرين اشتروا nft باموال طائلة ..😂 .. تخيل معي مالذي سيقود الصعود الجنوني للاسعار حاليا .. لا أحد يمكنه توقع اي فومو سيطلقونه خلال دورة البلران المتوقعة 👻 و لكن صدقني .. سينجحون في طلب شريحة طوييييلة و عريييضة من رؤوس أموال طازجة لتعليقها بالقمة... This is what they do..what they always do 😁

26 Jul 2025, 19:41 UTC652 viewsread 7 August 2026
Photo

شئنا أم أبينا .. Algotrade is the future of trading

14 Jul 2025, 06:28 UTC408 viewsread 7 August 2026
Photo

⚜️ BTC - USDT ⚜️ * شرح الصورة كتابيا * 📊 قاع البير ماركت 2015 : 1 - المدة الزمنية من قمة 2014 الى قاع 2015 =413 يوم . 2 - المدة الزمنية من قاع 2015 الى فاصل انقسام البتكوين الثاني =518 يوم . 3 - المدة الزمنية من قاع 2015 البير ماركت الى قمة البول ماركت ب2018 = 1064 يوم 4 - تقاطع نصف الدوائر الزمنية باللونين الابيض + الاصفر بالضبط في اقصى انخفاض لقاع بير ماركت 2015 📊 قاع البير ماركت 2018 : 1 - المدة الزمنية من ق

14 Jul 2025, 06:28 UTC655 viewsread 7 August 2026

20-08-2022 تاريخ نشر هذا التحلليل العملاق الذي اتحدى به اعتى المحللين في سوق الكريبتو

Showing the 12 most recent of 18 posts we hold for @SharkTrading. 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 — 893,293 of 1,583,249entries 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.

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.

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

“ՏHAƦK TƦADING” (@SharkTrading), 2,254 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/SharkTrading.

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.