Channel
@angel_engine_conf
On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,980subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002434358157 |
|---|---|
| Type | Channel |
| Username | @angel_engine_conf |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/angel_engine_conf |
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 10:48 | 1,980 | -7 |
| 8 Aug 2026, 01:21 | 1,987 | -1 |
| 7 Aug 2026, 15:47 | 1,988 | no change |
| 7 Aug 2026, 15:34 | 1,988 | first reading |
20 posts held, back to 2 May 2026 — 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 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 13 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
155 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 47.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 74 | 47.7% | |
| ❤ | 47 | 30.3% | |
| 💋 | 13 | 8.39% | |
| 💘 | 12 | 7.74% | |
| 🍌 | 3 | 1.94% | |
| 👏 | 3 | 1.94% | |
| 🥰 | 2 | 1.29% | |
| 🤡 | 1 | 0.645% |
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 14 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 155reactions 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 2 May 2026 to 13 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.
Неанон гугугага🥀🥀🥀 ссылка на мой тт если вам понравилось: https://www.tiktok.com/@gugugaga_77777?_r=1&_t=ZS-96W72qrvBWJ #тейк ∆×∆ @Agelenginecon_fbot
❤🔥12❤5💘5
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
ОДА МОЯ ЛЮБИМАЯ ГРУППА И ФД когда я услышала эту песню меня было не остановить неанон, автор: @bebebebedbeb /бебебешка #тейк ∆×∆ @Agelenginecon_fbot
❤🔥4💋3❤2
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
🤩Технолай к - мир, где ты можешь быть кем угодно и найти кучу друзей! 😗😂😋😉😌🙂😀😊😅 😅😚 Поделись своими мыслями, творчеством и идеями ЗДЕСЬ, а в ответ получи кучу сердееечеек(возможно....)!!!🌟🌟 НАВИГАЦИЯ 🌟 1. Взаимный пиар 2. @technolekebot 3. Чатик!!! 4. Правила 5. https://t.me/boost/tl_likecf АДМИНЫ🌟 Влд - менхантер Тейки - люстра Вп - кракен Модерация чата - Бебебе, Макуру
Signed K̼̺Ȑ̠̜A͗ͦK̼EͪͅN/##DICkLErr?!
Вот вам ещё Неанон гугугага🥀🥀🥀 ссылка на мой тт: https://www.tiktok.com/@gugugaga_77777?_r=1&_t=ZS-96W72qrvBWJ #тейк ∆×∆ @Agelenginecon_fbot
❤11❤🔥4💋2
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
Стивен Эклслэйность #тейк ∆×∆ @Agelenginecon_fbot
❤🔥8❤4
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
нарисовал нафотошопил и пох #тейк ∆×∆ @Agelenginecon_fbot
❤11💘7❤🔥5
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
Нарисовала Уриила как как вам☺ #тейк ∆×∆ @Agelenginecon_fbot
❤🔥11👏2🥰2
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
небольшой текст! анон пж Какофония из писка оборудования, шипения пара и грохота металла давила на мозг — отладка ангельского двигателя являлась не менее трудоемким процессом, чем сборка. Несмотря на то, что источник — в Вавилонской башне ангела называли только так — оставался неизменным, некоторые его… аспекты все еще были способны удивить. — Помоги мне, — прохрипел ангел, пытаясь дотянуться до размытого силуэта з…
❤🔥5
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
Подкружники простите что не выкладывали тейки сто лет
❤7❤🔥3🍌2
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
Всем приветик. Чтобы сделать небольшую активность кф, у меня вопрос. Что вы думаете насчёт последних серий, какой вы представляете финал и как будут развиваться следующие серии? #тейк ∆×∆ @Agelenginecon_fbot
❤🔥10👏1
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
Надеюсь вам понравится Неанон: Гугугага🥀🥀🥀 #тейк ∆×∆ @Agelenginecon_fbot
❤🔥11❤5💋4🍌1
Signed }❘{ęĤь𝙠ã Ø𝙘ё𝙩₱ ‡𖦹 ⋆｡°
TG‑Аккаунты ⭕ 🇩🇪 Германия ⪧ 319 ₽ | $4.19 🇺🇦 Украина ⪧ 279 ₽ | $3.69 🇯🇵 Япония ⪧ 249 ₽ | $3.29 🇰🇿 Казахстан ⪧ 239 ₽ | $3.19 🇹🇷 Турция ⪧ 209 ₽ | $2.79 🇺🇸 США ⪧ 59 ₽ TG‑Аккаунты США с отлёжкой ⭕ 2015 рег ⪧ 849 ₽ 2019 рег ⪧ 449 ₽ 2020 рег ⪧ 349 ₽
❤1🤡1
Signed K̼̺Ȑ̠̜A͗ͦK̼EͪͅN/##DICkLErr?!
Showing the 12 most recent of 20 posts we hold for @angel_engine_conf. 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.
Citation-graph rank — 788,406 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 registered channels — 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.
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.
“ANGEL ENGINE CONFESSIONS” (@angel_engine_conf), 1,980 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/angel_engine_conf.
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.