Telegram RegisterThe public register of Telegram
Telegram profile photo for REVENGE

Channel

REVENGE

@revengeeeeeeee

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

64subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001799237561
TypeChannel
Username@revengeeeeeeee
CreatedBetween 1 January 2022 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live21 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/revengeeeeeeee

Growth

636463.57 August 2026 — 63 subscribers10 August 2026 — 63 subscribers21 August 2026 — 64 subscribers7 August 202621 August 2026
3 measurements spanning 14 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 63–64 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 16:2964+1
10 Aug 2026, 03:3163no change
7 Aug 2026, 11:3463first reading

Engagement

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

What this channel posts

Video runtime
14s
Average length
14s

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.

Reaction mix

151 reactions across 18 posts, in 13 distinct kinds. The most used accounts for 14.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 58145938127139757962214.6%
custom 59114077915195684252214.6%
custom 59090078239241065771610.6%
1610.6%
custom 5814339460455732390138.61%
custom 5814266604925490604127.95%
custom 5366414971808790098117.28%
custom 522245231949645159395.96%
custom 582342359116468066995.96%
😍85.30%
🔥63.97%
🙏63.97%
🤝10.662%

Custom emoji. 8 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

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

16 Feb 2026, 10:54 UTC166 views6 reactionsread 10 August 2026
Photo

меня чет пиздец убила эта картинка

custom 59090078239241065773custom 59114077915195684252custom 52224523194964515931

4 Feb 2026, 08:47 UTC201 views9 reactionsread 10 August 2026

если че можете не искать меня в файлах Эпштейна, я двигаюсь тихо 🤫

custom 58142666049254906045custom 53664149718087900983custom 58143394604557323901

19 Jan 2026, 17:20 UTC213 views11 reactionsread 10 August 2026
Photo

djo - end of beginning

custom 58145938127139757965custom 58234235911646806693custom 59090078239241065773

16 Jan 2026, 08:44 UTC163 views8 reactionsread 10 August 2026
Photo

don’t be dumb ебанное мясо, обязательно к прослушиванию

custom 58145938127139757965🔥21

16 Jan 2026, 08:19 UTC115 views5 reactionsread 10 August 2026

асап роки - мессия американской рэп индустрии

🙏3🤝1😍1

13 Jan 2026, 09:43 UTC132 views13 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 59114077915195684255custom 590900782392410657743custom 52224523194964515931

31 Dec 2025, 21:09 UTC135 views13 reactionsread 10 August 2026

с новым годом пепе мои ♥️🎄

8🔥3😍2

30 Dec 2025, 13:36 UTC130 views12 reactionsread 10 August 2026

ехал пепе через шнейне видит пепе в шнейне фа сунул пепе руку в шнейне пепе шнейне ватафа

custom 58145938127139757967custom 59114077915195684253custom 58143394604557323902

24 Dec 2025, 13:05 UTC140 views6 reactionsread 10 August 2026
Video

Video, posted without a caption

🙏3😍2custom 59114077915195684251

23 Dec 2025, 10:54 UTC118 views7 reactionsread 10 August 2026

он долго молчал, чтобы вернуться и громко обосраться...♠

custom 52224523194964515934custom 53664149718087900982custom 59114077915195684251

23 Dec 2025, 10:50 UTC105 views8 reactionsread 10 August 2026
Photo

Новый год - время, когда мечты сбываются, вот я и подумал, почему бы не исполнить мечту моего друга и подписчика Данилы, преданного фаната музыкального ебланожурнала REVENGE Встречайте, рецензия на трек Ганвест - Вика любит ПЭПЭ «Вика пэпэ любит ПЭПЭ» — утраченный шнене манускрипт эпохи фо вотафо позднего хе гедонизма Перед нами — шнене не просто хе песня, а фо вотафо монумент пэпэ эпохи, где шнене автор, словно х

3custom 59090078239241065773custom 52224523194964515932

23 Dec 2025, 07:30 UTC83 views9 reactionsread 10 August 2026

итоги года этот канал все еще не закрылся

custom 58234235911646806696custom 53664149718087900982custom 59114077915195684251

Showing the 12 most recent of 18 posts we hold for @revengeeeeeeee. 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 21 August 2026 — this entry's latest reading, not the date you are reading this.

“REVENGE” (@revengeeeeeeee), 64 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/revengeeeeeeee.

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.