Telegram RegisterThe public register of Telegram
Telegram profile photo for YouTube ReVanced for Android 6-7

Channel

YouTube ReVanced for Android 6-7

@rvx_for_a6_7

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

2,724subscribers

-6 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001682744466
TypeChannel
Username@rvx_for_a6_7
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live29 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/rvx_for_a6_7

Growth

2,7212,7312,7267 August 2026 — 2,730 subscribers7 August 2026 — 2,730 subscribers10 August 2026 — 2,729 subscribers14 August 2026 — 2,731 subscribers17 August 2026 — 2,729 subscribers20 August 2026 — 2,727 subscribers23 August 2026 — 2,726 subscribers27 August 2026 — 2,721 subscribers29 August 2026 — 2,724 subscribers2,7247 August 202629 August 2026
9 measurements spanning 22 days, net -6. 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,720–2,733 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 17:572,724+3
27 Aug 2026, 04:252,721-5
23 Aug 2026, 19:032,726-1
20 Aug 2026, 13:542,727-2
17 Aug 2026, 14:342,729-2
14 Aug 2026, 07:082,731+2
10 Aug 2026, 17:462,729-1
7 Aug 2026, 16:272,730no change
7 Aug 2026, 15:172,730first reading

Engagement

17 posts held, back to 16 February 2025the 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 17 posts for this entry, the most recent from 18 June 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

821 reactions across 15 posts, in 21 distinct kinds. The most used accounts for 23.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
19223.4%
👍15518.9%
😭15118.4%
😢11514.0%
🔥516.21%
🤬303.65%
🕊293.53%
😱283.41%
🖕232.80%
🥰91.10%
💔70.853%
🤯70.853%
🫡70.853%
🤣50.609%
😁30.365%
👏20.244%
💋20.244%
😡20.244%
🌚10.122%
👎10.122%
1 further kind10.122%

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 15 of the 17 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 821reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 16 February 2025 to 18 June 2025, 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

18 Jun 2025, 12:31 UTC≈17,900 views130 reactionsread 7 August 2026
Photo

[News] YouTube 19.01.xx-19.19.xx died today! The force update screen (robot one) started to appear for these versions. At this time, there is no impact to 17.34.36. Spoofing to 19.01-19.19 is still possible because RVX Patch removes the robot screen. However, it is expected that 19.20 will be required soon. When this happens, we have no choice but to use broken visual styles.

😭7534👍7🖕6😢5💋2🔥1

14 May 2025, 11:59 UTC≈19,000 views41 reactionsread 7 August 2026
Photo

To change the video quality or playback speed, tap the video time. Long press the time to change video quality and playback speed. Also, enable RVX settings > Player > Player button > playback speed overlay button to change it easily.

👍2215🤣4

13 May 2025, 16:38 UTC≈16,900 views92 reactionsread 7 August 2026

Patches Update v5.6.2 https://github.com/kitadai31/revanced-patches-android6-7/releases/tag/v5.6.2 This update gives 17.34.36 a little extra life. Add missing resources, spoof app version, freeze server-side layouts. No more crashes with 19.01.34 spoofing. Read the instructions in this page carefully.

69👍8🤯7🔥4🥰3🤣1

24 Mar 2025, 18:49 UTC≈18,600 views27 reactionsread 7 August 2026

https://t.me/rvx_for_a6_7_chat/13633

🔥11🖕64👍4👏2

24 Mar 2025, 18:42 UTC≈16,000 views37 reactionsread 7 August 2026
Photo

Photo, posted without a caption

🔥25👍62🖕2😁1😱1

24 Mar 2025, 18:38 UTC≈25,800 views49 reactionsread 7 August 2026
Photo

Wow! I've never thought 19.05 is better than 19.01!!! Spoofing to 17.40-19.01 -> All Litho components disappear Spoofing to 19.05, 19.16 -> Design is broken, but Litho components are shown But there are still missing resources that causes crash Maybe I will try to ads resources

👍34🔥84🖕2🥰1

19 Mar 2025, 16:37 UTC≈12,000 views69 reactionsread 7 August 2026

Update: Library tab and video playback are not working too. (It seemed that it was working for me because my app had a cache.) All pages just show [400] error now. (Except home tab) Also, it started to get [400] error without Google accounts randomly! Clearing app data will not work gradually.

😢30😱16😭94🖕4👍2😡2🤔1

18 Mar 2025, 18:06 UTC≈11,400 views49 reactionsread 7 August 2026

Everyone, just use alternative ways! [Using youtube.com website] • Firefox + uBlock Origin + SponsorBlock + Return YouTube Dislike + Video Background Play Fix • Kiwi + uBlock Origin + SponsorBlock + Return YouTube Dislike (For Android 7.x, the final Kiwi 132 is available. But Android 6.0 can use up to Kiwi 107. I don't know if uBO works on Chromium 107.) If your device's SoC doesn't support VP9 hardware decoding, a

👍358🥰3😁2🖕1

18 Mar 2025, 17:34 UTC≈8,830 views20 reactionsread 7 August 2026

A TL;DR about this very long introduction: Q.What's the difference between this and other normal browsers? A. Other Chromium-based browsers are based on Chrome 119. (For Android 7) But Kiwi is Chrome 132. This post is not related to the 17.34.36 [400] error problem.

👍163🖕1

18 Mar 2025, 16:53 UTC≈8,720 views38 reactionsread 7 August 2026

This happened much sooner than I expected... At first I thought 17.34.36 would be usable until around July.

🤬18😢10😱5👍31🖕1

18 Mar 2025, 16:48 UTC≈14,400 views53 reactionsread 7 August 2026
Photo

Let me explain the current situation. • Google finally started to shutdown the old clients! • Old YouTube apps under v19.xx.xx are blocked by [400] error • This was being gradually rolled out to some Google accounts. • And this is now applied for most accounts. If your account is targeted: • The Home tab only shows "Switch to YouTube.com" • Most of other pages return a [400] errors • Only the Library tab and video

🕊27😢145👍5🌚1👎1

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

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

“YouTube ReVanced for Android 6-7” (@rvx_for_a6_7), 2,724 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/rvx_for_a6_7.

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.