Telegram RegisterThe public register of Telegram
Telegram profile photo for ?redfey

Channel

?redfey

@redfey

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

12subscribers

-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-1002085090040
TypeChannel
Username@redfey
Created5 May 2024 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 October 2026
Measurements held3
Confirmed unchanged2 times, most recently 12 October 2026
On Telegramt.me/redfey

Topic

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

Growth

121312.57 August 2026 — 13 subscribers12 August 2026 — 13 subscribers1 October 2026 — 12 subscribers7 August 20261 October 2026
3 measurements spanning 55 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 12–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 02:1612-1
12 Aug 2026, 03:3113no change
7 Aug 2026, 12:3613first reading

Engagement

11 posts held, back to 5 May 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 11 posts for this entry, the most recent from 5 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

130 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 44.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52761279173639725295844.6%
👍3426.2%
custom 52737768651510447212418.5%
custom 52739614972051646861410.8%

Custom emoji. 3 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 are Telegram’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 8 of the 11 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 130 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 5 May 2024 to 5 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

5 Feb 2026, 01:58 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

27 Jan 2026, 20:07 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 27 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

19 May 2024, 20:06 UTC102 views8 reactionsread 12 August 2026
Video

Video, posted without a caption

custom 52737768651510447215custom 52739614972051646862custom 52761279173639725291

Signed Bleykor

11 May 2024, 17:54 UTC202 views10 reactionsread 12 August 2026

Кладмен мудак

custom 52761279173639725295custom 52737768651510447214custom 52739614972051646861

Signed Bleykor

8 May 2024, 14:54 UTC242 views7 reactionsread 12 August 2026
Video

Video, posted without a caption

custom 52737768651510447213custom 52761279173639725293custom 52739614972051646861

Signed Bleykor

6 May 2024, 08:56 UTC244 views25 reactionsread 12 August 2026

Реакций уж ебаните

custom 527612791736397252916custom 52737768651510447215custom 52739614972051646864

Signed Bleykor

6 May 2024, 05:46 UTC271 views16 reactionsread 12 August 2026

Доброе утро

custom 527612791736397252912custom 52737768651510447212custom 52739614972051646862

5 May 2024, 22:44 UTC295 views12 reactionsread 12 August 2026

Если интересуют разные услуги к примеру: "деф" Обращаться — @bleykor

custom 52761279173639725298custom 52737768651510447212custom 52739614972051646862

5 May 2024, 22:28 UTC427 views14 reactionsread 12 August 2026

🦋 Мультичек на 1.999605 USDT ($2). Сумма одного чека: 0.01999 USDT ($0.02) Количество активаций: 100 💬 Столица России?

custom 52761279173639725299custom 52737768651510447213custom 52739614972051646862

5 May 2024, 21:00 UTC345 views38 reactionsread 12 August 2026

30 реакций и начнем

👍34custom 52761279173639725294

Showing the 11 most recent of 11 posts we hold for @redfey. 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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“?redfey” (@redfey), 12 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/redfey.

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.