https://x.com/Crypto_Pranjal/status/2017026676253946306?s=20

Channel
AIRDROP ADAMINSSANE AA
@Adaminsane
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
134subscribers
+0 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 | -1001178806005 |
|---|---|
| Type | Channel |
| Username | @Adaminsane |
| Description | 👀 AIRDROP ADAMINSSANE FR.OG - Free Cryptos, Tokens & Coin - Group Discuss: https://t.me/airdropcryptodiscuss 👥 Aide, stratégies et astuces. 📌 TRADING, INVESTISSEMENT & AIRDROP. https://t.me/Adaminssane1 |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Adaminsane |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 00:01 | 134 | no change |
| 6 Aug 2026, 14:34 | 134 | first reading |
Engagement
15 posts held, back to 7 December 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 30 January 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈6,660
- Videos
- ≈4
- Links
- ≈6,460
Lifetime counters from Telegram’s own channel header, read 9 August 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.
Recent posts
https://x.com/Crypto_Pranjal/status/2003204755548700773?s=20
Airdrop checker : zkPass Total supply : 1B https://airdrop.zkpass.org/
Nouveau Airdrop : La pépite cachée pour les traders Perp Si tu as déjà tradé sur un Perp DEX… tu es peut-être assis sur des Rails Points gratuits 👀⚡️ Rails (@rails_xyz) vient de lancer Rails ID, un perp DEX hybride soutenu par 20M$ (Kraken, Slow Ventures, etc.). Voici l’alpha : - Connecte ton compte X + ton wallet EVM principal → points instantanés basés sur ton volume et tes fees passés. - Quêtes supplémentaires …
Je fais souvent +50$ à +100$ sur mes 3 vaults, puis quelques heures plus tard mon PnL retombe à -25$ ou -50$. C’est normal si je laisse mes trades ouverts trop longtemps après que l’écart maximal de mon hedge ait déjà été atteint. Désormais, dès que j’atteins +60$ (par exemple), je sécurise immédiatement une partie du profit : - Je ferme 50% tout de suite - Je ferme 30% après une heure - Je ferme les 20% restants…
Inverssion du Signal sur SOLBNB : Short SOL & Long BNB Short SOL (Market Entry) TP1 : 136.15$ → 40% TP2 : 131.62$ → 30% TP3 : 126.82$ → 10% TP4 : Laisser courir → 10% Long BNB (Market Entry) TP1 : 927.55$ → 40% TP2 : 948.73$ → 30% TP3 : 970.96$ → 10% TP4 : Laisser courir → 10%
J'ai atteint 3 TP sur Short ETH et Long BNB dans mon Vault ETHBNB et j'ai tout clôturé pour réouvrir un nouveau Hedge Les 3 TP étaient sur Short ETH avant hier et 2 TP sur le Long BNB aujourd'hui
J'ai atteint 3 TP dans mon Vault ETHSOL et j'ai tout clôturé pour ouvrir un nouveau Hedge Les 3 TP étaient sur Short ETH avant hier et Long SOL hier et aujourd'hui
TP 1 et 2 sur Long SOL ✅
TP 1 sur Long BNB ✅
Mise à jour Trades : Stratégie Hedging (ETH/BNB & SOL/BNB) Basé sur mon indicateur + même logique que mes vaults. Je partage ici mes entrées, mes TP et ma gestion en transparence. 1️⃣ Position : Long BNB & Short ETH Long BNB (Market Entry) TP1 : 900.01$ → 40% TP2 : 921.05$ → 30% TP3 : 938.81$ → 10% TP4 : Laisser courir → 10% Short ETH (Market Entry) TP1 : 3,025.07$ → 40% TP2 : 2,831.56$ → 30% TP3 : 2,736.65$ → 10…
Le marketing “0% fees” de Lighter est en réalité l’un des pièges les plus coûteux en crypto. Le vraie “fee” sur Lighter, c’est la latence, et 300 ms c’est catastrophique. Exécution lente = mauvais fills, slippage caché, et un coût 5 à 10 fois plus élevé que de payer des frais normaux. J’ai testé Lighter il y a quelques semaines. Les fills étaient tellement mauvais que je suis parti directement. Rien n’est vraiment …
Showing the 12 most recent of 15 posts we hold for @Adaminsane. 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“AIRDROP ADAMINSSANE AA” (@Adaminsane), 134 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Adaminsane.
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.