Telegram RegisterThe public register of Telegram

Channel

Offensive OSINT

@offensiveosint

On this record: Growth · Engagement · Posts · Citations · Cite this entry

3,652subscribers

+25 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001706113747
TypeChannel
Username@offensiveosint
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/offensiveosint

Growth

3,6273,6523,639.56 August 2026 — 3,627 subscribers6 August 2026 — 3,627 subscribers6 August 2026 — 3,632 subscribers9 August 2026 — 3,649 subscribers13 August 2026 — 3,652 subscribers6 August 202613 August 2026
5 measurements spanning 7 days, net +25. 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 3,623–3,656 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 02:483,652+3
9 Aug 2026, 19:123,649+17
6 Aug 2026, 14:403,632+5
6 Aug 2026, 04:343,627no change
6 Aug 2026, 03:203,627first reading

Engagement

22 posts held, back to 25 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.56%
avg views ÷ 3,652 subscribers
Avg views / post
276
22 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
22
of 22 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held22 (25 July 20267 August 2026)
Views total6,078
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 22:59 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

7 Aug 2026, 13:51 UTC92 viewsread 7 August 2026
Photo

TrafficVision Агрегатор дорожных камер: 155 000+ живых фидов из 700+ официальных источников по 130+ странам. Все американские DOT и 511-системы (Caltrans, TxDOT, FDOT, 511NY и остальные) сведены в одну карту, плюс европейские и прочие транспортные ведомства. Без регистрации. Фильтры по стране, штату, локации и типу фида. Есть построитель маршрутов, который выдаёт все камеры вдоль заданного пути - удобно, когда нужн

6 Aug 2026, 10:54 UTC154 viewsread 7 August 2026
Photo

OSINT Cabal Email Kit Веб-обёртка, которая гоняет пять почтовых тулз параллельно по одному адресу: Holehe, Zehef, Hashtray, Mailsleuth и HaveIBeenPwned. Без установки, результаты стримятся в браузер по мере обхода. На выходе два блока: зарегистрированные площадки (где на этот email заведён аккаунт, с пометкой какой тулзой найдено) и найденные утечки с указанием источника. Плюс сводка со счётчиками. ➡️ https://osin

5 Aug 2026, 15:59 UTC177 viewsread 7 August 2026
Photo

WARP Веб-архив Национальной парламентской библиотеки Японии - японский аналог Wayback Machine, работает с 2003 года. Архивирует японские сайты: госорганы, местные администрации, госкорпорации, университеты, партии, компании. Полезно там, где Wayback по японским сайтам пустой: архивация ведётся по закону о библиотеке, охват госресурсов глубже. ➡️ https://warp.ndl.go.jp/ #osint #archives #japan #tools 📱 Offensive

5 Aug 2026, 09:04 UTC225 viewsread 7 August 2026
Photo

WebVetted: анализ Instagram-аккаунта Прогоняет @username по 12 проверкам и отдаёт отчёт с сигналами риска. Ориентировано на проверку на фейк, накрутку и импersonation. Что смотрит: соотношение вовлечённости к числу подписчиков, возраст аккаунта, признаки ботов и купленных фолловеров, реальное имя за юзернеймом, аккаунты на других площадках, вытаскивание почт и ссылок из био, реверс-поиск по аватарке, детект украден

4 Aug 2026, 15:59 UTC249 viewsread 7 August 2026
Photo

OSINT Lens Расширение для Chrome: выделяешь на любой странице имя, юзернейм, почту или номер телефона - и в один клик прогоняешь по открытым OSINT-источникам. ➡️ https://chromewebstore.google.com/detail/osint-lens/ocknklpfmnemcchnkbnjdakmfckhcndn #osint #recon #tools #chrome 📱 Offensive OSINT

4 Aug 2026, 08:59 UTC256 viewsread 7 August 2026
Photo

Flock Camera Map Карта задокументированных камер слежения по адресу в США: считыватели автомобильных номеров Flock, обычные камеры, датчики выстрелов и камеры скорости. Плюс показывает, какие программы наблюдения ведёт местная полиция. Бесплатно, без регистрации. Данные по камерам берутся из OpenStreetMap, размечены в основном силами сообщества DeFlock. Есть отдельный слой Privacy - все 3143 округа США со скорингом

3 Aug 2026, 15:59 UTC255 viewsread 7 August 2026
Photo

Digital Footprints: разбор термина Статья от The OSINT Group о том, что цифровой след - это не только соцсети. Разложены активные следы (посты, комментарии, регистрации, отзывы) и пассивные, которые генерятся сами: куки, фингерпринт браузера, логи IP, метаданные, геолокация, разрешения приложений. Основная мысль - про корреляцию. Один юзернейм, почта, аватарка или манера письма, повторяющиеся на разных площадках, п

3 Aug 2026, 15:45 UTC200 viewsread 7 August 2026
Photo

Немножко мемов в тяжёлый понедельник 📱 Offensive OSINT

3 Aug 2026, 09:04 UTC233 viewsread 7 August 2026
Photo

Binalyze Outpost Расширение для Chrome, которое превращает любую веб-страницу в рабочее место аналитика. Сканирует страницу на индикаторы компрометации, подсвечивает их прямо в тексте и обогащает через внешние источники, не выходя из вкладки. Ловит IPv4/IPv6, домены, URL и хэши файлов (MD5, SHA1, SHA256). Результаты уходят в боковую панель браузера с поиском, фильтрацией и группировкой по типам, нужные наблюдаемые

2 Aug 2026, 10:08 UTC245 viewsread 7 August 2026
Photo

autoDNA Собирает данные из 26+ стран Европы, США и Канады - госреестры, страховые, сервисы, техосмотры. 50 000+ источников на 500+ млн машин. В отчёте: смена владельцев, ДТП, график пробега по датам, базы угона, заводская комплектация, архивные фото. Для США - отметки Junk, Salvage, Total loss. Отдельно любопытна история проверок самого VIN с картой: много запросов из разных мест означает либо частую смену владельц

1 Aug 2026, 11:46 UTC272 viewsread 7 August 2026
Photo

SubCat Веб-обёртка для SubCat - тулзы поиска субдоменов. Вбиваешь домен прямо в браузере, результаты идут в реальном времени в живой терминал, без установки. ➡️ https://osintcabal.org/livecenter/subcat.html #osint #recon #bugbounty #tools 📱 Offensive OSINT

31 Jul 2026, 15:59 UTC345 viewsread 7 August 2026
Photo

OpenTor Позволяет агентам ИИ получать доступ к Tor для OSINT, кибербезопасности и анализа данных. Имеет функции поиска в даркнете и извлечения индикаторов компрометации. ➡️ https://github.com/vichhka-git/OpenTor #osint #ai #darkweb 📱 Offensive OSINT

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

Citation-graph rank

Citation-graph rank — 116,572 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 12 registered channels — 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.

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

“Offensive OSINT” (@offensiveosint), 3,652 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/offensiveosint.

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.