Channel
@IntelFetch
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
4,718subscribers
-145 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002096279475 |
|---|---|
| Type | Channel |
| Username | @IntelFetch |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/IntelFetch |
Hacking & security — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 02:17 | 4,718 | -70 |
| 14 Sept 2026, 02:39 | 4,788 | -14 |
| 10 Sept 2026, 00:21 | 4,802 | -4 |
| 5 Sept 2026, 03:15 | 4,806 | -15 |
| 1 Sept 2026, 12:05 | 4,821 | -8 |
| 29 Aug 2026, 06:08 | 4,829 | -7 |
| 26 Aug 2026, 14:13 | 4,836 | -11 |
| 20 Aug 2026, 01:56 | 4,847 | -9 |
| 16 Aug 2026, 17:56 | 4,856 | +1 |
| 13 Aug 2026, 11:18 | 4,855 | -4 |
| 10 Aug 2026, 17:35 | 4,859 | -2 |
| 8 Aug 2026, 03:01 | 4,861 | -2 |
| 7 Aug 2026, 13:17 | 4,863 | first reading |
20 posts held, back to 26 February 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pages 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 20 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
🥳 Update - 5th of August 2026 Changes • Added 1.9 billion stealer logs, currently adding another 1 billion, and will of course ingest more fresh after that. • Real Time Data Modules, added 2 new modules. IP Address search, and Domain search, with very good modules for those two :) Crypto & Card Payments Available - intelfetch.net Contact @IntelFetchSupportBot for API volume or custom inquiries.
🥳 Update - 19th of July 2026 AI OSINT Changes: • Changed the AI model to a better AI model. • Made it server-side ran, you no longer need to stay on the page to get the results. Most importantly, we made it be able to intake more information, so you can a more precise, and more intelligent search. Crypto & Card Payments Available - intelfetch.net Contact @IntelFetchSupportBot for API volume or custom inquiries.
🥳 Update - 6th of July 2026 Shop & pricing improvements are live. • API Access, $200/mo self-serve checkout in Shop (new or extend existing key). • Referrers now earn 10% wallet credit on referral purchases (auto-credited, usable in Shop) Find plans at intelfetch.net/pricing, more updates coming soon. Crypto & Card Payments Available - intelfetch.net Contact @IntelFetchSupportBot for API volume or custom inquirie…
🥳 Update - 13th of June 2026 We've added a new feature: Log Search. Search leaked credentials from credential dumps (ULP, browser exports) by URL, email, username, or password. Results include the source URL, credential type, login, password, and when the record was indexed, with human-readable dates in the results view. Find it in Standard Features on the tools dashboard. Crypto & Card Payments Available - intel…
👑 Update - 31st of May 2026 We've indexed over 31.000 new files (datasets) into Fetchbase, and we'll continue to index more. We've also fixed a bug where you'd get logged out quite often. Happy summer everyone, use the code "SUMMER25" to get 25% off ANYTHING in the shop, you may use the coupon as many times as you wish, the last coupon in a while publicly announced :) Expires in 24 hours. Crypto & Card Payments A…
👑 Update - 18th of May 2026 We've added 2 new features and improved one of our free features. Introducing email validation, input an email and receive if its a valid mail, if it's disposable, SMTP records, MX records and its metadata. MAC Address Lookup, input a mac address and find out manufacturer/vendor of it, also reports whether its locally administered or multicast. We've also added WHOIS records to our fre…
💎 Update - 15th of May 2026 New subscription tiers are live. Quick backstory: since November 2025 our costs have gone up over 500%. We purchased a legitimate IntelligenceX license and integrated every endpoint, making IntelFetch one of the only OSINT services with a fully licensed IntelX integration, along with other costs making IntelFetch better. We wanted to do this the right way. To keep the lights on and keep…
✨ Update - 9th of May 2026 We've changed away from our old Result displayer, resorting to a much more organized displayer for the results, optimized for each feature. We've also fixed a numerous bugs, applied security patches and made it a generally smoother experience. Crypto & Card Payments Available - intelfetch.net Contact @IntelFetchSupportBot for API or custom inquiries.
also fixed a small bug regarding the IntelX Stealer Log Download :)
✨ Update - 3rd of May 2026 We've renamed the subscription based (no credits) Phone OSINT Modules to Basic Real Time Intelligence and we've added Email Search to it :) This is also added to the API, and can be used as many times as you wish (with fair use policies*) Crypto & Card Payments Available - intelfetch.net Contact @IntelFetchSupportBot for API or custom queries.
✨ Update - 23rd of April 2026 AI OSINT has gotten a HUGE update. We've 10x'ed the context gathered from our sources into what the AI can process. Using various fragmenting techniques, we've made the context limit from 800k token limit all the way up to 8 million token limit! And of course with no extra cost to the user :) Enjoy a way better AI OSINT today. Crypto & Card Payments Available - intelfetch.net Contact…
✨ Update - 12th of April 2026 AI OSINT has just gotten a phone number alternative, being very effective as it has depth searching, once it finds terms. AI Image Geolocation has just gone from 15 credits per search, to 3 credits per search, an 80% reduction on the price. We've also fixed some small bugs. Crypto & Card Payments Available - intelfetch.net Contact @IntelFetchSupportBot for API.
Showing the 12 most recent of 20 posts we hold for @IntelFetch. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“IntelFetch Announcements” (@IntelFetch), 4,718 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/IntelFetch.
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.