Telegram RegisterThe public register of Telegram
Telegram profile photo for IntelSec

Channel

IntelSec

@IntelligenceSec

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

615subscribers

-50 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-1001943205219
TypeChannel
Username@IntelligenceSec
Created29 April 2023 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live13 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/IntelligenceSec

Topic

Marketing & affiliate — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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

6156656407 August 2026 — 665 subscribers8 August 2026 — 665 subscribers14 August 2026 — 661 subscribers22 August 2026 — 655 subscribers29 August 2026 — 648 subscribers7 September 2026 — 642 subscribers14 September 2026 — 639 subscribers28 September 2026 — 633 subscribers9 October 2026 — 628 subscribers16 October 2026 — 625 subscribers22 October 2026 — 623 subscribers29 October 2026 — 621 subscribers5 November 2026 — 618 subscribers13 November 2026 — 615 subscribers7 August 202613 November 2026
14 measurements spanning 98 days, net -50. 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 608–673 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 20:21615-3
5 Nov 2026, 10:09618-3
29 Oct 2026, 22:17621-2
22 Oct 2026, 13:38623-2
16 Oct 2026, 04:56625-3
9 Oct 2026, 09:19628-5
28 Sept 2026, 13:01633-6
14 Sept 2026, 20:20639-3
7 Sept 2026, 08:40642-6
29 Aug 2026, 06:04648-7
22 Aug 2026, 03:34655-6
14 Aug 2026, 20:56661-4
8 Aug 2026, 02:34665no change
7 Aug 2026, 12:25665first reading

Engagement

17 posts held, back to 29 April 2023 — 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 page of 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 17 posts for this entry, the most recent from 8 January 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
53s
Average length
53s

Measured directly from 1 video 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

8 Jan 2025, 12:59 UTC≈1,010 viewsread 8 August 2026

selling project channel for 6k with old source + bot without keys, previously sold source for 20k with keys @hgfdskgfg

2 Aug 2023, 14:33 UTC≈17,100 viewsread 8 August 2026

Everything going back to normal, use @intelsec_bot and intelsec.mysellix.io if you want to purchase intelsec (repost) - @Lonely

19 Jun 2023, 15:26 UTCviews —

IntelSec pinned «$500 Crypto Giveaway Giveaway conditions: • Must be inside @intelligencesec Number of Participants: 812 To participate in the giveaway, press the button below!»

19 Jun 2023, 15:26 UTC≈21,800 viewsread 8 August 2026

$500 Crypto Giveaway Giveaway conditions: • Must be inside @intelligencesec Number of Participants: 812 To participate in the giveaway, press the button below!

16 Jun 2023, 11:21 UTC≈20,000 viewsread 8 August 2026

Hello, IntelSec is now up. We're working on fixing our MS module, IntelX credits are drained for the day, sorry. Usernames won’t work on LC for a bit too. DM @Lonely for your plan back, adding five days to each person when i’m not busy

14 Jun 2023, 17:26 UTC≈14,700 viewsread 8 August 2026

Hey! Looking for a developer experienced with python & golang :P If you're wondering why there's been so much down time lately, we've been experimenting with migration, we'll add however many days we’re online to everyone's monthly plans when the bot is up (~3 days)

10 Jun 2023, 21:54 UTC≈12,000 viewsread 8 August 2026
Photo

Started working on the site a few hours ago, started from scratch, should be done in a few weeks.

10 Jun 2023, 14:55 UTC≈9,990 viewsread 8 August 2026

Hey there Intelsec buyers! We've fixed the Gmail module so you can use it without problems. We're working on fixing the LinkedIn module and will keep you posted. As a thank you for bearing with us, we're adding an extra week to every monthly plan. Thanks for your continued support! Gmail ✅ LinkedIn ❌ (Soon)

22 May 2023, 15:09 UTC≈10,400 viewsread 8 August 2026

PM @Lonely or visit https://intelsec.mysellix.io to buy.

22 May 2023, 15:00 UTC≈9,310 viewsread 8 August 2026

Exciting news! We are introducing IntelX to our service, marking a significant leap forward in IntelSec. We want to ensure you are fully prepared for this game-changing advancement. Please keep in mind that IntelX will be exclusively available in our lifetime plan and will not be included in the monthly subscription.

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

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“IntelSec” (@IntelligenceSec), 615 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/IntelligenceSec.

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.