Telegram RegisterThe public register of Telegram
Telegram profile photo for ranfren

Channel

ranfren

@ranfrennnn

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

8,764subscribers

-37 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001714079452
TypeChannel
Username@ranfrennnn
Descriptionглавы на русском языке до 27 люсида взяты из группы вк" MonteGlover и его друзьяхи"(https://vk.com/monteglover ) разрешения нет тк спрашивать ссусь, меня отпиздят, главы на англ взяты с оф сайта ранфрен, ну забейте в гугле мне лень ссылку искать😘
Created5 January 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live22 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/ranfrennnn

Growth

8,7648,8018,782.56 August 2026 — 8,801 subscribers6 August 2026 — 8,801 subscribers6 August 2026 — 8,800 subscribers9 August 2026 — 8,793 subscribers13 August 2026 — 8,790 subscribers16 August 2026 — 8,777 subscribers19 August 2026 — 8,773 subscribers22 August 2026 — 8,764 subscribers6 August 202622 August 2026
8 measurements spanning 16 days, net -37. 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 8,758–8,807 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 14:028,764-9
19 Aug 2026, 12:368,773-4
16 Aug 2026, 21:288,777-13
13 Aug 2026, 04:278,790-3
9 Aug 2026, 22:318,793-7
6 Aug 2026, 14:528,800-1
6 Aug 2026, 10:178,801no change
6 Aug 2026, 09:468,801first reading

Engagement

3 posts held, back to 17 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 24 pagesof 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 3 posts for this entry, the most recent from 1 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1,590
Links
6

Lifetime counters from Telegram’s own channel header, read 25 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

1,945 reactions across 3 posts, in 11 distinct kinds. The most used accounts for 41.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
80941.6%
❤‍🔥36318.7%
🐳30115.5%
🎉27314.0%
🔥804.11%
🤔693.55%
🍌170.874%
😁140.72%
👏100.514%
👍60.308%
🥰30.154%

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

Measured over the 3 most recent posts we hold, published 17 September 2025 to 1 October 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

1 Oct 2025, 16:52 UTC≈19,000 views781 reactionsread 25 August 2026
Photo

Photo, posted without a caption

444🎉144❤‍🔥105🤔41🔥15🐳12🍌9😁8

1 Oct 2025, 16:52 UTC≈18,500 views553 reactionsread 25 August 2026
Photo

люсид 34 англ

317🎉110❤‍🔥75🤔22🐳8🔥7👏6🍌4

17 Sept 2025, 07:30 UTC≈19,300 views611 reactionsread 25 August 2026

33 люсид файл не открывается тк он неправильный, так что пока ждем апдейт:выйдет 30 числа глава

🐳281❤‍🔥183🔥5848🎉19🤔6😁6🍌4

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

“ranfren” (@ranfrennnn), 8,764 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/ranfrennnn.

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.