Telegram RegisterThe public register of Telegram

Channel

Iran OWASP Chapter

@irOWASP

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

695subscribers

+1 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001013500259
TypeChannel
Username@irOWASP
Created18 February 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/irOWASP

Growth

694695694.55 August 2026 — 694 subscribers6 August 2026 — 694 subscribers13 August 2026 — 695 subscribers5 August 202613 August 2026
3 measurements spanning 7 days, net +1. 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 694–695 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 06:56695+1
6 Aug 2026, 16:37694no change
5 Aug 2026, 22:23694first reading

Engagement

19 posts held, back to 5 December 2018the 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 19 posts for this entry, the most recent from 5 October 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Oct 2021, 22:56 UTC≈5,890 viewsread 6 August 2026

Test your services against the latest Apache vulnerability CVE-2021-41773 with OWASP Nettacker. https://twitter.com/razielowfsky/status/1445519591283691529 @irOWASP

22 Sept 2021, 18:44 UTC≈4,900 viewsread 6 August 2026

Join our live conference about Nettacker in OWASP LA (starts in 1min) https://twitter.com/securestep9/status/1440236301660262405?s=21 @irOWASP

9 Sept 2021, 21:10 UTC≈3,960 viewsread 6 August 2026

OWASP Nettacker now migrated to YAML-Based modules, many code enhancements and improvements, and x3 faster than before. https://github.com/OWASP/Nettacker 🔗 @irOWASP

28 Dec 2020, 11:05 UTC≈4,480 viewsread 6 August 2026

Good time to contribute to open source, even if are not an expert in programming it’s a prefect chance to help us in tests and user experiences also learning more about the project. https://twitter.com/razielowfsky/status/1343512748399931393?s=21 🔗 @irOWASP

15 Sept 2020, 19:00 UTC≈4,580 viewsread 6 August 2026

OWASP Honeypot Demo https://twitter.com/razielowfsky/status/1305936838234910725?s=20 🔗 @irOWASP

4 Apr 2020, 17:34 UTC≈5,410 viewsread 6 August 2026

در این بخش ها نیاز به کمک هست که میتواند شروع همکاری در اواَسپ باشد. * code review and manual testing PRs (22 tasks) https://github.com/zdresearch/OWASP-Nettacker/pulls * fix or/and adding new features (59 tasks). https://github.com/zdresearch/OWASP-Nettacker/issues * review and manual testing PRs (4 tasks) https://github.com/zdresearch/OWASP-Honeypot/pulls * fix or/and adding new features (6 tasks) https://github.

4 Apr 2020, 17:20 UTC≈3,900 viewsread 6 August 2026
File

توضیحات در مورد فعالیت در اواَسپ 🔗 @irOWASP

3 Apr 2020, 22:33 UTC≈3,860 viewsread 6 August 2026

متاسفانه ویدئو لایو دوم بنده به دوستان بر خورده ظاهرا و از آفسک پاک شده، من از کسانی که ناراحت شدند عذرخواهی میکنم و یک سری نکات را یادآوری خواهم کرد: * بنده هدفم انتقاد از مدیریت بود و نه تخریب مرکز ماهر * بنده با محمد جرجندی رفیق نیستم، و ایشون نیاز ندارند که ۴ تا مخاطب من یا آفسک اسمش را بشنوند، فقط کارهای ایشون را دنبال میکنم چون دروغی درش نیست و همه با سند و مدرک هستند. * بنده از طرف آفسک و اوَسپ صحبت نکردم، هم

3 Apr 2020, 20:14 UTC≈3,430 viewsread 6 August 2026
Photo

مقاله‌ای از محمدرضا اسپرغم، علی رزمجو، احسان نظامی در آخرین نسخه از مجله‌ی پنتست‌مگ، یکی از پرمخاطب‌ترین مجلات امنیت اطلاعات با موضوع پروژه نرم‌افزاری OWASP JoomScan 🔗 @irOWASP

2 Apr 2020, 13:02 UTC≈4,680 viewsread 6 August 2026
Video

ارائه علی رزمجو با موضوع رویکرد عملی برای برنامه ریزی آموزشی با هدف مهاجرت 🔗 @irOWASP

20 Oct 2019, 22:05 UTC≈4,250 viewsread 6 August 2026
Photo

OWASP JoomScan coming soon... Stay tuned! https://twitter.com/rezesp/status/1186040959030775815 #JoomScan [We Will Become Ourselves Reborn] 🔗 @irOWASP #infosec #joomla #perl

7 May 2019, 12:14 UTC≈4,640 viewsread 6 August 2026
Photo

OWASP Python Honeypot project selected for Google summer of code and we got one student, thanks to GSoC, OWASP for such great support. https://twitter.com/razielowfsky/status/1125721412881268736 🔗 @irOWASP #GSoC #GoogleSummerOfCode

Showing the 12 most recent of 19 posts we hold for @irOWASP. 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 — 745,222 of 1,345,403entries 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.

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

“Iran OWASP Chapter” (@irOWASP), 695 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/irOWASP.

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.