Telegram RegisterThe public register of Telegram
Telegram profile photo for اینترنت ازاد

Channel

اینترنت ازاد

@mitivpn

Not marked by Telegram, checked 21 August 20262 usernames

On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts edited after publishing · Citations · Domains linked from posts · Cite this entry

2,465,646subscribers

-42,030 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1002258272508
TypeChannel
Usernames@mitivpn @net_azad
DescriptionFAST MTPROTO PROXIES FOR TELEGRAM اینترنت آزاد برای همه, یا هیچکس کانفیگ اختصاصی : @mitivpnbot
Created9 January 2025 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held95
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/mitivpn

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 78% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 3 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@mitivpn/18449 · this entry5 Sept 2026, 16:44 UTC@AarazV2ray/72015 Sept 2026, 17:12 UTC1.0029 minutes
@mitivpn/18507 · this entry11 Sept 2026, 18:10 UTC@AarazV2ray/742611 Sept 2026, 18:50 UTC1.0040 minutes
@mitivpn/18822 · this entry20 Oct 2026, 15:28 UTC@AarazV2ray/851020 Oct 2026, 15:42 UTC1.0013 minutes
@mitivpn/18857 · this entry22 Oct 2026, 09:16 UTC@AarazV2ray/856922 Oct 2026, 09:32 UTC1.0016 minutes
@mitivpn/18640 · this entry29 Sept 2026, 17:36 UTC@AarazV2ray/790329 Sept 2026, 17:37 UTC0.9872 seconds
@mitivpn/18700 · this entry9 Oct 2026, 16:14 UTC@AarazV2ray/82299 Oct 2026, 16:18 UTC0.934 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@AarazV2ray6 (6/6 hand-verifiable sample passed)0.9914 minutesthis entry (6–0)
@mazenehtaaalaa6 (6/6 hand-verifiable sample passed)1.004 minutesthis entry (6–0)
@frenetvpn5 (5/5 hand-verifiable sample passed)1.0029 minutesthis entry (5–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 474 comparable posts for this entry, running 22 December 2025 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

2,371,3132,535,7712,453,5422,465,6466 August 202610 November 2026
95 measurements spanning 96 days, net -42,030. 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 2,346,644–2,560,440 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 95
Measured (UTC)SubscribersChange
10 Nov 2026, 10:452,465,646-880
10 Nov 2026, 01:202,466,526-2,908
9 Nov 2026, 00:172,469,434-625
8 Nov 2026, 19:282,470,059-2,919
7 Nov 2026, 20:102,472,978-1,575
7 Nov 2026, 11:472,474,553-2,630
6 Nov 2026, 17:302,477,183-845
6 Nov 2026, 13:392,478,028-3,115
5 Nov 2026, 18:162,481,143-1,399
5 Nov 2026, 12:172,482,542-2,916
4 Nov 2026, 15:112,485,458-709
4 Nov 2026, 10:242,486,167-1,721
3 Nov 2026, 17:262,487,888-1,487
3 Nov 2026, 06:552,489,375-2,086
2 Nov 2026, 15:162,491,461-926
2 Nov 2026, 09:412,492,387-3,472
1 Nov 2026, 13:162,495,859-764
1 Nov 2026, 08:162,496,623-3,368
31 Oct 2026, 10:562,499,991-1,123
31 Oct 2026, 04:402,501,114first reading

Engagement

811 posts held, back to 9 January 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4,210 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.15%
avg views ÷ 2,465,646 subscribers
Avg views / post
226,000
190 posts measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
190
of 811 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. It is computed over the 187 of 190 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 November 2026
Posts held811 (9 January 2025 – 10 November 2026)
Views total42,859,543
Reactions total493,877
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 07:45 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.

What this channel posts

Links
321

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
13m 19s
Average length
44s

Measured directly from 18 videos 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.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 189 of this channel’s own posts over the last 30 days: across 16 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 40 hours of being posted; a typical post has already reached 23.1% of its 24-hour view count within the first hour, and 59.0% within the first six; the median 24-hour reach across those posts is 471,500 views — 19.1% of this channel’s own subscriber count (90th percentile 580,000).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/1905110 Nov 2026, 20:08 UTC17 minutes – 7 minutes old33,400 views ~144 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/1905010 Nov 2026, 20:01 UTC114 minutes – 14 minutes old60,400 views ~436 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/190459 Nov 2026, 10:02 UTC13 minutes – 3 minutes old11,200 views ~598 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/190429 Nov 2026, 09:41 UTC1225 minutes – 7.1 hours old210,000 views ~1,103 reactions60 minutes: 98,339 interp. → 3.0 hours: 162,531 interp. → 6.0 hours: 197,711 interp.still climbing at last readingnot yet at 24h64 minutesprovisional — final view count still climbing
/190378 Nov 2026, 18:18 UTC23 minutes – 57 minutes old103,000 views ~7,587 reactions60 minutes: 103,000not yet at 24h26 minutesprovisional — final view count still climbing
/190368 Nov 2026, 15:18 UTC122 minutes – 22 minutes old75,300 views ~4,027 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/190357 Nov 2026, 20:34 UTC17 minutes – 7 minutes old55,700 views ~2,148 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/190347 Nov 2026, 20:31 UTC110 minutes – 10 minutes old81,000 views ~1,358 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

1,863,544 reactions across 537 posts, in 28 distinct kinds. The most used accounts for 39.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣736,00939.5%
❤287,69515.4%
💔201,38610.8%
👍176,0339.45%
👎112,1526.02%
🔥83,8394.50%
🖕75,2444.04%
❤‍🔥63,6863.42%
😐63,4093.40%
⚡20,1671.08%
💩14,1220.758%
😭8,7640.47%
🍓4,6870.252%
😈4,4010.236%
👌3,6510.196%
🆒2,9490.158%
🗿8850.047%
🎃8630.046%
😍7300.039%
🤬6540.035%
8 further kinds2,2180.119%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 806 of the 811 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3,805,983 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 811 most recent posts we hold, published 9 January 2025 to 10 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 81 of 190 posts held from the last 30 days (42.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 20:08 UTC≈33,400 views144 reactionsread 10 November 2026

مخصوص شرایط اعتراضات و جنگ

❤92👍33⚡10🔥9

10 Nov 2026, 20:01 UTC≈60,400 views436 reactionsread 10 November 2026

🔴 طبق گفته کاربران اینترنت تو بعضی از نقاط کشور، ضعیف شده امشب و اختلال زیادی داره! این رباتمون رو داشته باشید خدایی نکرده قطع نشید : 🤖 @mitivpnbot

👍346❤66⚡19🔥5

9 Nov 2026, 10:02 UTC≈11,200 views598 reactionsread 9 November 2026

🔴 پزشکیان: برازنده ما نیست با وجود امکانات و منابع سرشار مردم با مشکل مواجه باشن.

🤣452💔56👍51❤39

9 Nov 2026, 09:41 UTC≈210,000 views1,103 reactionsread 9 November 2026
File

🏆 کانفیگ نپستر برای تمامی اپراتور ها نامحدود مولتی لوکیشن اختصاصی و آیپی ثابت مخصوص دانلود وب گردی برای اندروید و آیفون 🔴کانفیگی که توی شرایط بحرانی کشور وصله! نحوه اتصال داخل اندروید👉 نحوه اتصال داخل آیفون👉 اینترنت آزاد برای همه, یا هیچکس 👑 T.me/MiTiVPN

❤954👍76⚡37🔥36

Signed ꜱʜᴀʜ

8 Nov 2026, 18:18 UTC≈103,000 views7,587 reactionsread 8 November 2026

امن ترین جای دنیا زیر پتو با شارژ ۱۰۰درصده

👍6,000❤752🤣676💔159

8 Nov 2026, 15:18 UTC≈75,300 views4,027 reactionsread 8 November 2026
Photo

🔴 توی سایتای شرط بندی، شانس حمله آمریکا به ایران تا قبل از اومدن کنگره جدید به 11 درصد رسید و 89 درصد مردم جهان معتقدن دیگه به ایران حمله نمیشه.

🤣2,790💔879👎199❤159

7 Nov 2026, 20:34 UTC≈55,700 views2,148 reactionsread 7 November 2026

🔴 صداوسیما : صدای انفجاری که تو جاسک، سیریک، بندرعباس و قشم شنیده شد بخاطر مدیریت تنگه ی هرمز توسط ایرانه.

🤣1,890👎108❤95👍55

7 Nov 2026, 20:31 UTC≈81,000 views1,358 reactionsread 7 November 2026

🔴فوری سنتکام: ۵ سکوی پرتاب موشک در جاسک و یک رادار در قشم را دقایقی قبل مورد هدف قرار دادیم.

❤699🤣302💔258👍99

7 Nov 2026, 20:24 UTC≈111,000 views1,640 reactionsread 7 November 2026

🔴 صداوسیما انفجار در جاسک، سیریک، بندرعباس و قشم رو تأیید کرد.

🤣978💔380👍143❤139

7 Nov 2026, 20:22 UTC≈245,000 views934 reactionsread 8 November 2026
File

🏆 کانفیگ نپستر برای تمامی اپراتور ها نامحدود مولتی لوکیشن اختصاصی و آیپی ثابت مخصوص دانلود وب گردی برای اندروید و آیفون 🔴کانفیگی که توی شرایط بحرانی کشور وصله! نحوه اتصال داخل اندروید👉 نحوه اتصال داخل آیفون👉 اینترنت آزاد برای همه, یا هیچکس ⚡️ T.me/MiTiVPN

🔥764⚡70😈50🆒50

7 Nov 2026, 17:39 UTC≈76,200 views2,353 reactionsread 7 November 2026

🔴 مدیرعامل شرکت ملی گاز: قبض گاز مشترکان پرمصرف‌ با تعرفه نزدیک به قیمت صادرات محاسبه می‌شود.

😐1,690🤣438👍134👎91

7 Nov 2026, 16:49 UTC≈4,840 views18 reactionsread 7 November 2026

🔴 طبق گفته کاربران اینترنت تو بعضی از نقاط کشور، ضعیف شده امشب و اختلال زیادی داره! این رباتمون رو داشته باشید خدایی نکرده قطع نشید : 🤖 @mitivpnbot

👍10⚡7❤1

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

Posts edited after publishing

@mitivpn edited 52 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
7 August 2026
Most recent edit
10 November 2026

Mentions

Named by 75 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Domains linked from posts

4 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

lmarena.ai1 post · 7 August 2026 – 7 August 2026 · example post
www.lovart.airegistrable domain: lovart.ai1 post · 7 August 2026 – 7 August 2026 · example post
yupp.ai1 post · 7 August 2026 – 7 August 2026 · example post
zenmux.ai1 post · 7 August 2026 – 7 August 2026 · example post

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

“اینترنت ازاد” (@mitivpn), 2,465,646 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/mitivpn.

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.