Telegram RegisterThe public register of Telegram
Telegram profile photo for Szellima ໒ Ꮚ ´‌ ᵕ ‌ ꒱ work

Channel

Szellima ໒ Ꮚ ´‌ ᵕ ‌ ꒱ work

@angeldevilslove

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

1subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003105215828
TypeChannel
Username@angeldevilslove
DescriptionInfo @tomurashigarakitruelover Dm @shimuratenkoirl Credit Lynkjin on x
Created20 October 2025measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live19 September 2026
Measurements held2
On Telegramt.me/angeldevilslove

Growth

112 August 2026 — 1 subscribers15 August 2026 — 1 subscribers12 August 202615 August 2026
2 measurements spanning 3 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 10:161no change
12 Aug 2026, 19:491first reading

Engagement

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

What this channel posts

Photos
1
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

8 Apr 2026, 06:30 UTC300 viewsread 15 August 2026
Photo

Credit 🌟Фулл список всех кн где я работала/работаю и тд Щас работаю: @hatemhacm (в заморозке ща), @daily_castodei (влд) , @dailyblafka , @dailyruanherta , @sunvencfxday , , @cfdailyruanmei , @TRIGGERMHA @DailyTomuraShiggy ( влд) ) , @da1lyblade @Mgacanons , @dailymizihyuna Работала @cyrenedaily , @dailycfevernight , @daily_bootheng , @LOVEMHACM , @lukatilldaily_ss , @kokomidailyy @dailyciphlaea, @DailyConst

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

Names

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

♡゙ㅤ 𝐛𝐥𝐚𝐝𝐞 ֺ 𝒹𝒶𝒾𝓁𝓎 ۪𝒸𝒻
@da1lyblade · 783
1 post
ֺ 𝑏𝑜𝑜𝑡ℎ𝑒𝑛𝑔 ♡゙ 𝒹𝒶𝒾𝓁𝓎 𝒸𝒻 ⚙️🍁
@daily_bootheng · 704
1 post
ֺ 𝑐𝑎𝑠𝑡𝑜𝑑𝑒𝑖 ♡゙ 𝒹𝒶𝒾𝓁𝓎 𝒸𝒻 🍷🦋
@daily_castodei · 639
1 post
ֺ 𝑑𝑎𝑛𝑚𝑎𝑟𝑐ℎ ♡゙ 𝒹𝒶𝒾𝓁𝓎 𝒸𝒻 🍁🌸
@daily_danmarch · 1,427
1 post
ֺ 𝑝ℎ𝑎𝑖𝑟𝑒𝑛𝑒 ♡゙ 𝒹𝒶𝒾𝓁𝓎 𝒸𝒻 ☀️🌾
@daily_phairene · 922
1 post
꒰ ֺ 𝐄𝐯𝐞𝐫𝐧𝐢𝐠𝐡𝐭 𝐃𝐚𝐢𝐥𝐲×𝐜𝐟 ⏝
@dailycfevernight · 1,196
1 post
ㅤ ݃ 𝒸𝒻 𝑑𝑎𝑖𝑙𝑦 ♡゙ 𝒄𝒊𝒑𝒉𝒍𝒂𝒆𝒂
@dailyciphlaea · 951
1 post
✧⁠*⁠。Daily & cf The Dahlia /Constance
@DailyConsta · 998
1 post
.
@dailyflauma · 3
1 post
♡゙ㅤ 𝐤𝐚𝐟𝐤𝐚 ֺ 𝒹𝒶𝒾𝓁𝓎 ۪𝒸𝒻
@dailykafka · 1,015
1 post
◞ 𝗇𝗈𝗇-𝖽𝖺𝗂𝗅𝗒 𝗆𝗂𝗓𝗂𝗁𝗒𝗎𝗇𝖺 ♡
@dailymizihyuna · 1,118
1 post
ㅤ ִִ 𝒓𝐮𝐚𝐧𝐡𝐞𝐫𝐭𝐚 ♡⃘ ‌ׄ 𝓭𝒂𝒊𝒍𝒚 ִִ 𝒸𝒇 ׄ
@dailyruanherta · 1,727
1 post
𝖳𝗈𝗆𝗎𝗋𝖺 𝑑𝑎𝑖𝑙𝑦
@DailyTomuraShiggy · 235
1 post
𝅄ㅤ𝐳𝐚𝐧𝐢ㅤ ִ 𝒅𝒂𝒊𝒍𝒚𝑐𝑓 ݄
@dailyZaniwuwa · 442
1 post
♡゙𝒟𝒶𝓃𝐻𝑒𝓃𝑔⋮ Danheng daily
@DanHengcfdaily · 978
1 post
ᅠ♡゙ ׄ 𝐄𝐯𝐞𝐫𝐧𝐢𝐠𝐡𝐭 ׅ 𝑑𝑎𝑖𝑙𝒚
@evernightdaily_com · 1,458
1 post
HATE MHA community
@hatemhacm · 122
1 post
ㅤ⁠⁠⁠𝐡𝐞𝐫𝐭𝐚𝐦𝐞𝐢 ⋮ 𝒹𝒶𝒾𝓁𝓎𝐜𝐟ㅤ⁠⁠⁠
@hertameidaily · 1,911
1 post
ㅤ𝗄𝖺𝒻𝗌𝗍𝖾𝗅 ݁݁ㅤִ 𝖽𝖺𝗂𝗅𝗒𝖼𝒻ㅤ
@kafstellovers · 1,130
1 post
ПЕРЕЕЗД ПЕРЕЕЗДㅤㅤ◟𐐪 𝑲𝒐𝒌𝒐𝒎𝒊 𝒹𝒶𝒾𝓁𝓎 ɞ◞ ♡⃕
@kokomidailyy · 583
1 post
LOVE! MHA COMMUNITY
@LOVEMHACM · 261
1 post
♡ ݄ 𝐥𝐮𝐤𝐚𝐭𝐢𝐥𝐥 ֺᅠ 𝑑𝑎𝑖𝑙𝑦𝒸𝒻
@lukatilldaily_ss · 2,035
1 post
ʏᴏᴜʀ ꜰᴀᴠᴏʀɪᴛᴇ ᴍʜᴀ ᴄᴀɴᴏɴs♡゙̼
@Mgacanons · 143
1 post
TRIGGER MY HERO ACADEMIA 💥
@TRIGGERMHA · 711
1 post

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.

“Szellima ໒ Ꮚ ´‌ ᵕ ‌ ꒱ work” (@angeldevilslove), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/angeldevilslove.

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.