Telegram RegisterThe public register of Telegram
Telegram profile photo for 👨‍🚀 REV HUNTER VPN [OFICIAL]

Channel

👨‍🚀 REV HUNTER VPN [OFICIAL]

@RevHunter

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

36,278subscribers

-1,438 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001761793234
TypeChannel
Username@RevHunter
Description👨‍🚀 Novidades e Avisos sobre o Rev Hunter https://play.google.com/store/apps/details?id=com.hunter.net 👨‍💻 Site ➡️ https://revhuntervpn.com 💬 Grupo Oficial @REVHUNTERGRUPO ✉️ Email Empresarial [email protected] 🏆 Design J.K @JKCRIATIVOS
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/RevHunter

Topic

Technology — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 85% 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.

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 word for word on 1 other registered channel. 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@RevHunter/2094 · this entry12 Mar 2026, 20:59 UTC@RevSocksHttp/1331112 Mar 2026, 20:59 UTC1.00under a minute
@RevHunter/2134 · this entry29 May 2026, 22:03 UTC@RevSocksHttp/1332429 May 2026, 22:03 UTC1.00under a minute
@RevSocksHttp/133304 Aug 2026, 21:36 UTC@RevHunter/2152 · this entry4 Aug 2026, 21:37 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@RevSocksHttp6 (6/6 hand-verifiable sample passed)1.00under a minuteeven

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 3 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 16 comparable posts for this entry, running 1 January 2026 to 4 August 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).

Across the whole group of 2, the earliest publisher we hold is @RevSocksHttp. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

36,27837,71636,9976 August 2026 — 37,716 subscribers6 August 2026 — 37,716 subscribers7 August 2026 — 37,672 subscribers8 August 2026 — 37,639 subscribers9 August 2026 — 37,615 subscribers10 August 2026 — 37,593 subscribers11 August 2026 — 37,579 subscribers12 August 2026 — 37,508 subscribers13 August 2026 — 37,477 subscribers15 August 2026 — 37,442 subscribers16 August 2026 — 37,377 subscribers17 August 2026 — 37,350 subscribers18 August 2026 — 37,293 subscribers19 August 2026 — 37,268 subscribers20 August 2026 — 37,205 subscribers22 August 2026 — 37,165 subscribers24 August 2026 — 37,119 subscribers25 August 2026 — 37,071 subscribers26 August 2026 — 37,040 subscribers27 August 2026 — 37,024 subscribers28 August 2026 — 37,010 subscribers29 August 2026 — 36,985 subscribers30 August 2026 — 36,951 subscribers31 August 2026 — 36,911 subscribers1 September 2026 — 36,849 subscribers1 September 2026 — 36,795 subscribers3 September 2026 — 36,775 subscribers4 September 2026 — 36,746 subscribers8 September 2026 — 36,677 subscribers11 September 2026 — 36,583 subscribers13 September 2026 — 36,529 subscribers14 September 2026 — 36,487 subscribers16 September 2026 — 36,424 subscribers18 September 2026 — 36,377 subscribers25 September 2026 — 36,278 subscribers6 August 202625 September 2026
35 measurements spanning 50 days, net -1,438. 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 36,062–37,932 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
25 Sept 2026, 03:5936,278-99
18 Sept 2026, 17:1936,377-47
16 Sept 2026, 10:3836,424-63
14 Sept 2026, 13:4236,487-42
13 Sept 2026, 00:3736,529-54
11 Sept 2026, 00:3936,583-94
8 Sept 2026, 01:5936,677-69
4 Sept 2026, 22:3936,746-29
3 Sept 2026, 05:5436,775-20
1 Sept 2026, 22:0436,795-54
1 Sept 2026, 01:0836,849-62
31 Aug 2026, 00:0636,911-40
30 Aug 2026, 02:2436,951-34
29 Aug 2026, 01:3536,985-25
28 Aug 2026, 03:3837,010-14
27 Aug 2026, 07:0537,024-16
26 Aug 2026, 05:4337,040-31
25 Aug 2026, 05:3337,071-48
24 Aug 2026, 00:5637,119-46
22 Aug 2026, 06:0537,165first reading

Engagement

31 posts held, back to 1 January 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 98 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.21%
avg views ÷ 36,278 subscribers
Avg views / post
3,340
6 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
6
of 31 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 26 September 2026
Posts held31 (1 January 2026 – 26 September 2026)
Views total20,050
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Sept 2026, 05:27 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

Photos
319
Videos
24
Links
98

Lifetime counters from Telegram’s own channel header, read 30 September 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
18s
Average length
18s

Measured directly from 1 video 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.

Recent posts

26 Sept 2026, 01:50 UTC≈1,700 viewsread 30 September 2026
Photo

😕 As Conexões TIM AZN e XRAY foram bloqueadas pela operadora. 🔵 Mas ainda há várias conexões funcionando no Rev... 💜 Abra a lista de Conexões, teste as opções e descubra qual funciona melhor na sua região!

24 Sept 2026, 18:59 UTC≈2,170 viewsread 30 September 2026

💜 Em caso de qualquer problema, entre em contato pelo e-mail [email protected] ou pelo bot @FeedbackRevHunterBOT, enviando detalhes, prints e/ou vídeos.

24 Sept 2026, 18:59 UTC≈2,210 viewsread 30 September 2026
Photo

👾 Atualização Disponível! ✅ Versão: 47 • Conexão aprimorada • Suporte a IPv6 no túnel • Melhorias e outras correções ⚠️ Após atualizar, é recomendável limpar o cache e os dados do aplicativo caso ele apresente erros. 💜 Se algum problema persistir, tente reinstalar o aplicativo e repetir o processo, se necessário. Clique no Link: 👇 https://play.google.com/store/apps/details?id=com.hunter.net

20 Sept 2026, 23:58 UTC≈3,340 viewsread 30 September 2026

👾 Melhor operadora no Rev? 🔵 Atualmente, a TIM (com saldo válido) é a melhor opção para usar a VPN. Diversas conexões funcionando bem. 🤔 • Mas o que é saldo válido? É quando você faz uma recarga e ela ainda está dentro do prazo de validade. Pode até ter só 1 centavo de crédito — estando válido, já funciona!

18 Sept 2026, 21:36 UTC≈3,890 viewsread 30 September 2026
Photo

🔵 Conexão TIM 2.1 (CDN TLS) adicionada! • Saldo Válido • Saldo Expirado 🔄 Clique no 'ATUALIZAR' e teste! 💜 Disponível apenas na última versão do Rev.

1 Sept 2026, 23:50 UTC≈6,740 viewsread 30 September 2026
Photo

🔵 Conexão TIM 1.1 (XRAY|MUX) adicionada! 🤓 É uma variante da TIM 01 (XRAY), com uma diferença: 🔹 TIM 01: várias sessões curtas 🔹 TIM 1.1: uma sessão longa 💜 Por favor, teste as duas e escolha a que melhor funcionar na sua região, disponível apenas na última versão do Rev.

29 Aug 2026, 00:05 UTC≈6,720 viewsread 30 September 2026

💜 Em caso de qualquer problema, entre em contato pelo e-mail [email protected] ou pelo bot @FeedbackRevHunterBOT, enviando detalhes, prints e/ou vídeos.

28 Aug 2026, 23:43 UTC≈6,500 viewsread 30 September 2026
Photo

👾 Atualização Disponível! ✅ Versão: 46 • Correção de erro na abertura • Suporte pra BRISANET adicionado 🟠 • Melhorias e outras correções ⚠️ Após atualizar, é recomendável limpar o cache e os dados do aplicativo caso ele apresente erros. 💜 Se algum problema persistir, tente reinstalar o aplicativo e repetir o processo, se necessário. Clique no Link: 👇 https://play.google.com/store/apps/details?id=com.hunter.net

27 Aug 2026, 01:45 UTC≈5,720 viewsread 30 September 2026

💜 Boa noite! 😶‍🌫️ Em alguns celulares após a atualização o aplicativo tem travado antes mesmo de iniciar, estou tentando identificar o problema pra enviar uma nova atualização o mais rápido possível. 🫡 Assim que resolver vou avisar aqui no canal.

26 Aug 2026, 04:56 UTC≈6,770 viewsread 30 September 2026
Photo

👾 Atualização Disponível! ✅ Versão: 44 • Conexões mais estáveis • Melhorias e correções de erros • Atualização de bibliotecas ⚠️ Após atualizar, é recomendável limpar o cache e os dados do aplicativo caso ele apresente erros. 💜 Se algum problema persistir, tente reinstalar o aplicativo e repetir o processo, se necessário. Clique no Link: 👇 https://play.google.com/store/apps/details?id=com.hunter.net

21 Aug 2026, 01:24 UTC≈6,970 viewsread 30 September 2026
Photo

💜 DICA TIM! 🔵 Pra TIM tente usar as Conexões: • TIM 01 (XRAY|MULTI) • TIM 02 (FLARE TLS) 🚀 Faça o teste na sua região!

10 Aug 2026, 20:49 UTC≈8,960 viewsread 30 September 2026
Photo

💜 Gere Números Virtuais e E-mails temporários pra receber códigos de verificação! 💬 1000+ Serviços disponíveis 🌏 190+ Países disponíveis 💜 Acesse o Hunter SMS pra gerar números e e-mails temporários. • Bot: @revhuntersmsbot

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

@RevHunter edited 2 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
9 September 2026
Most recent edit
26 September 2026

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

“👨‍🚀 REV HUNTER VPN [OFICIAL]” (@RevHunter), 36,278 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/RevHunter.

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.