7 Mar 2026, 18:27 UTC211 viewsread 9 August 2026
INFILTRA is now part of NeXa! Join the channel to stay updated with all news and updates: https://t.me/NeXaGate/
Channel
infilTra
@getInfiltra
On this record: Growth · Engagement · Posts · Citations · Cite this entry
119subscribers
+0 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 | -1002535898664 |
|---|---|
| Type | Channel |
| Username | @getInfiltra |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/getInfiltra |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 21:44 | 119 | -1 |
| 16 Aug 2026, 08:15 | 120 | +1 |
| 9 Aug 2026, 04:32 | 119 | no change |
| 7 Aug 2026, 17:16 | 119 | first reading |
Engagement
9 posts held, back to 3 August 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 9 posts for this entry, the most recent from 7 March 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
2 Jan 2026, 21:06 UTC276 viewsread 9 August 2026
Forwarded from @NeXaGateway
Introducing NeXa (Next Level Data) We are ready to release the release of NeXa, a bot designed to help you explore vast datasets, logs, courses, data archives, and more, faster than ever. (over 350k files.) Why NeXa? We built NeXa to solve the problem of cluttered, slow, and unreliable data searching of Telegram, with our own datasets. Capabilities: Precise Querying: Search specifically for .csv, .txt, .sql and an…
13 Nov 2025, 22:57 UTCviews —
Posted without readable text
10 Nov 2025, 14:25 UTC342 viewsread 9 August 2026
🔎 We will soon rework the sign-up and login pages to implement UUID based accounts, addressing the issues related to email registration.
9 Oct 2025, 18:18 UTC443 viewsread 9 August 2026
🔎 Fix: Resolved a problem in which numerical limit value were not correctly scaled after downloading results.
7 Oct 2025, 20:32 UTC488 viewsread 9 August 2026
🔎 Hotfix: Resolved an issue preventing emails from being sent due to a configuration typo. Sorry for the time! You can now sign up.
7 Oct 2025, 15:00 UTC≈1,090 viewsread 9 August 2026
🔎 Infiltra Update! Changelog: • Database Searches (45B+ entries) • Landing Page enhancements • FAQ Page updates • Updated Documentation • Numerous UI improvements • Bug fixes and performance optimizations • And more For full details, visit: https://infiltra.do/# > FAQ > Docs > Pricings > Records
1 Sept 2025, 12:36 UTC454 viewsread 9 August 2026
🔎 Explorer Sale is Live! Monthly Plan: 50% off Quarterly Plan: 20% off Annual Plan: 10% off Check out the offers here: https://infiltra.do/#pricing
3 Aug 2025, 18:11 UTC≈2,790 viewsread 9 August 2026
Photo
🔎 infiltra.do // @getInfiltra – an OSINT search engine optimized for high‑volume breach data analysis. Implements SHA‑256 hashing for strict deduplication, ensuring unique record retrieval even across heterogeneous data sources. Current index records: >47,000,000,000 normalized and verified entries. Datasets: ULP – URL:Login:Password Combolists – Login:Password Databases – Email, Phone, Username, IP, URL Real‑time …
Showing the 9 most recent of 9 posts we hold for @getInfiltra. 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.
Forward network
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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“infilTra” (@getInfiltra), 119 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/getInfiltra.
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.