Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝒜𝓃ℊℯ𝓁𝒾𝓃𝒶 𝒥ℴ𝒽𝓃𝓈ℴ𝓃🥂

Channel

𝒜𝓃ℊℯ𝓁𝒾𝓃𝒶 𝒥ℴ𝒽𝓃𝓈ℴ𝓃🥂

@angellelele67

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

34subscribers

-1 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003726599071
TypeChannel
Username@angellelele67
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live30 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/angellelele67

Growth

34363514 August 2026 — 35 subscribers16 August 2026 — 36 subscribers30 August 2026 — 34 subscribers14 August 202630 August 2026
3 measurements spanning 15 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 34–36 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 07:2934-2
16 Aug 2026, 15:0636+1
14 Aug 2026, 23:3135first reading

Engagement

19 posts held, back to 10 August 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
38.6%
avg views ÷ 34 subscribers
Avg views / post
13.1
17 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
17
of 19 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held19 (10 August 202614 August 2026)
Views total223
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 23:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
26s
Average length
13s

Measured directly from 2 videos 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.

Recent posts

14 Aug 2026, 23:21 UTC1 viewsread 14 August 2026
Forwarded from @bliznezi67

https://t.me/twins_weasly2 вот ребят, человек попросил создать новых, вот

14 Aug 2026, 17:04 UTC11 viewsread 14 August 2026

я предлагаю устроить внеплановые каникулы

14 Aug 2026, 15:38 UTC4 viewsread 14 August 2026
Forwarded from @mattheor1ddleVideo

ㅤ ㅤ ๋ 𝖠𝖲𝖲𝖮𝖢𝖨𝖠𝖳𝖨𝖮𝖭𝖲 ⏝ "кто вы из мультсериала аркейн?" условия: ¹. быть подписанным ². репост к себе в канал ³. + с ссылкой или от лица тгк 6/10

14 Aug 2026, 15:04 UTC3 viewsread 14 August 2026
Forwarded from @ewmisliznortFile

File, posted without a caption

14 Aug 2026, 15:03 UTC2 viewsread 14 August 2026
Forwarded from @raspredelyutebya

давайте пацаны слово дадим что Ералаша не забудем

14 Aug 2026, 12:04 UTC17 views0 reactionsread 14 August 2026

ты промто босс

Signed @𝗺𝗶𝗿𝗲𝗹'.𝘄𝗹S

14 Aug 2026, 11:58 UTC8 viewsread 14 August 2026
Forwarded from @fleurslayy

с днем наркомана пупсы

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“𝒜𝓃ℊℯ𝓁𝒾𝓃𝒶 𝒥ℴ𝒽𝓃𝓈ℴ𝓃🥂” (@angellelele67), 34 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/angellelele67.

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.