Telegram RegisterThe public register of Telegram

Channel

Ангельские глаза

@angelseye1

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

26subscribers

+0 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-1003729004111
TypeChannel
Username@angelseye1
CreatedBetween 1 February 2026 and 22 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/angelseye1

Growth

267 August 2026 — 26 subscribers11 August 2026 — 26 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 25–27 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 08:3426no change
7 Aug 2026, 19:0726first reading

Engagement

20 posts held, back to 22 April 2026the 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 20 posts for this entry, the most recent from 25 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Videos
30
Links
3

Lifetime counters from Telegram’s own channel header, read 11 August 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.

Reaction mix

10 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 90.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
990.0%
custom 5222196489769469693110.0%

Custom emoji. One row above is a 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 count beside it isTelegram’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 7 of the 20 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 10reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 22 April 2026 to 25 June 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

25 Jun 2026, 04:46 UTC43 views1 reactionsread 11 August 2026

Новости: У нас нью #Лили Влд #ангелок

1

25 Jun 2026, 02:25 UTC49 viewsread 11 August 2026

Новости У нас Нью #КАНИБАЛ // влд #ангелок

22 Jun 2026, 22:11 UTC58 viewsread 11 August 2026

Старые админы напишите пожалуйста в бот, я вас добавлю в админы. #ангелок

22 Jun 2026, 00:15 UTC56 views1 reactionsread 11 August 2026

Новости: У нас нью #крыса // влд #ангелок

custom 52221964897694696931

21 Jun 2026, 19:05 UTC50 viewsread 11 August 2026

Всем здравствуйте ищем админов в наш бот #ангелок

21 Jun 2026, 04:38 UTC54 viewsread 11 August 2026

Ребята бот открылся снова #ангелок

13 May 2026, 03:14 UTC91 viewsread 11 August 2026

Новости : Администратор #слезы берет рест на 2 дня // Влд 2 #ⲙⲉⲣⲧⲃⲁя

12 May 2026, 13:29 UTC82 views1 reactionsread 11 August 2026

Новости : у нас нью #сталкер // Влд 2 #ⲙⲉⲣⲧⲃⲁя

1

26 Apr 2026, 10:58 UTC108 views1 reactionsread 11 August 2026

Новости #смерть берет рест до 30

1

24 Apr 2026, 14:53 UTC121 views3 reactionsread 11 August 2026

Новости 2влд вернулся #мёртвая

3

24 Apr 2026, 12:13 UTC114 views2 reactionsread 11 August 2026

Новости у нас новый админ #слезы

2

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“Ангельские глаза” (@angelseye1), 26 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/angelseye1.

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.