SATAN IND pinned a video

Channel
SATAN IND
@satanind
On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry
313subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001940282931 |
|---|---|
| Type | Channel |
| Username | @satanind |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/satanind |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 04:56 | 313 | -3 |
| 14 Aug 2026, 17:05 | 316 | -2 |
| 8 Aug 2026, 07:32 | 318 | no change |
| 7 Aug 2026, 12:34 | 318 | first reading |
Engagement
16 posts held, back to 18 June 2024 — 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 16 posts for this entry, the most recent from 27 July 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 2m 29s
- Average length
- 1m 15s
Measured directly from 2 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.
Recent posts
We introduce to you, XeinHax-DFM with the best quality 🌟 •Smooth ESP •Powerfull AIM-BOT •Aimbot touch simulation (Root) •Aimbot memory 1.1(Root and Non-root) •All aimbots are equipped with recoil compensation rules, Aim prediction, •Strong bypass update by online server •Support root and Non-Root (No need -Virtual) » Price List Promo New Release For Customer « 1 day - 25.000 | $3 3 day - 50.000 | $5 7 days - 120.00…
Channel name was changed to «SATAN IND»
We introduce to you, XeinHax-DFM with the best quality 🌟 •Smooth ESP •Powerfull AIM-BOT •Aimbot touch simulation (Root) •Aimbot memory 1.1 •All aimbots are equipped with recoil compensation rules, Aim prediction, •Strong bypass update by online server • ONLY Support root 64 BIT » Price List Promo New Release For Customer « 1 day - 25.000 | $3 3 day - 50.000 | $5 7 days - 120.000 | $9 14 days - 200.000 | $13 30 days…
Sticker, posted without a caption
Fek
Satan ready!!
Photo, posted without a caption
Photo, posted without a caption
This Aim touch is 🔥🔥😈
Photo, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 16 posts we hold for @satanind. 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.
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.
“SATAN IND” (@satanind), 313 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/satanind.
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.