Telegram RegisterThe public register of Telegram
Telegram profile photo for INFO

Channel

INFO

@infoangelsden

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

7subscribers

+0 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1002698136412
TypeChannel
Username@infoangelsden
Created17 May 2025measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live8 September 2026
Measurements held2
On Telegramt.me/infoangelsden

Growth

715 Aug 2026, 06:51 — 7 subscribers15 Aug 2026, 07:00 — 7 subscribers15 Aug 2026, 06:5115 Aug 2026, 07:00
2 measurements taken within a single day. 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 6–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 07:007no change
15 Aug 2026, 06:517first reading

Engagement

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

What this channel posts

Links
1

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

Recent posts

23 Feb 2026, 15:02 UTC221 viewsread 15 August 2026

chats Angel’s Den первый - вирт заявки подаем онли в один чат, иначе не примут второй - нотвирт

22 Sept 2025, 18:18 UTC382 viewsread 15 August 2026

Initials ang & angel ангельский & ангельская при нажатии копируется важно! инициалы ставятся только в ник, в био можно только юз кф!

22 Sept 2025, 18:15 UTC383 viewsread 15 August 2026

Admins one chat owner- @GUCCUUH старший админ- админ по чату- админ по активу- админ по нью- админ по союзам- Admins two chat owner- @GUCCUUH старший админ- админ по чату- админ по активу- админ по нью- админ по союзам-

22 Sept 2025, 18:14 UTC330 viewsread 15 August 2026

UNION’S Rules О1.папка рп О2.1:1 О3.союзы 0+ О4.пост о заключении с нашей стороны О5.можем отказать в заключение союза если ваш кф связан с рейд деятельностью. О6.разрыв если: 1.чат со следящем удален 2.допы отписаны 3.неуважительное отношение О7.всю важную информацию и рп кидать в лс, иначе потом не обижайтесь, что мы не делаем рп писать: @GUCCUUH О1. пост о заключение держим час О2. рп держим 2 часа О3.публикую

22 Sept 2025, 18:13 UTC273 viewsread 15 August 2026

RULES Chat -за что можно получить мут? О1. тема религий/любой вид филии. О2. после произошедшего конфликта, вы все равно продолжаете мусолить тему. О3. оскорбления участников, чрезмерное употребление «черного» юмора. -за что я могу получить пред? О1. оскорбление/неуважение к администрации либо же в сторону участников. О2. участие в конфликте. особо разбираться кто прав-кто виноват не буду. пред летит всем, кто разв

22 Sept 2025, 10:47 UTC189 viewsread 15 August 2026

P̼͂͝À͇͋T̜͕̑É̻ͪN̫ͥ̕T̡̮̩ 20.09.2025 — С €Т0Г0 ДНЯ К0НФ3Р3НЦ1Я ”ANGEL’S DEN” Б3Р3Т П4Т3НТ Н4 Н4ЗВ4Н13 И 0Ф0РМЛ3Н13 КФ В ЛЮБ0М Ф0РМ4Т3.(ANGEL’S DEN, АНГЕЛЬСКИЙ ПРИТОН, ЛОГОВО АНГЕЛА, АНГЕЛЬСКИЕ И ТД) 3СЛ1 МЫ УВ1Д1М П0Д0БН03 0Ф0РМЛ3Н13 1Л1 Н4ЗВ4Н13, ТО БУД3М ВЫНУЖД3НЫ П0ПР0СИТЬ СМ3Н1ТЬ Т0, ЧТ0 ВЗЯЛ1.

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

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.

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

“INFO” (@infoangelsden), 7 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/infoangelsden.

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.