Telegram RegisterThe public register of Telegram
Telegram profile photo for Ambivalence.

Channel

Ambivalence.

@miexture

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

8subscribers

+0 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1001567279662
TypeChannel
Username@miexture
CreatedBetween 1 August 2021 and 8 May 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live1 September 2026
Measurements held2
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/miexture

Growth

831 Aug 2026, 06:47 — 8 subscribers1 Sept 2026, 05:26 — 8 subscribers31 Aug 2026, 06:471 Sept 2026, 05:26
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 7–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 05:268no change
31 Aug 2026, 06:478first reading

Engagement

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

What this channel posts

Video runtime
15s
Average length
15s

Measured directly from 1 video 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

12 May 2022, 14:45 UTC339 viewsread 31 August 2026

[] Hallo, this is Alàfki's mundane speaking. Due to my personal reasons, today I decided to leave this roleplayer world. Thank you for existence me and I’m sorry if I make some mistakes, which is intentionally or not. Minta maaf sebesar-besarnya yaa. Thank you to all who have become family, friends, and others being good to me. Thanks yoo dh nemenin selama main RP. I’m so lucky to met you guys. So yeaah, finally! I c

12 May 2022, 09:58 UTC309 viewsread 31 August 2026

ㅤㅤㅤㅤㅤㅤ𝗚𝘂𝗶𝗱𝗲 𝘁𝗼 𝗠𝗮𝘁𝘂𝗿𝗮𝘁𝗶𝗼𝗻. ਏਓ ⋆ The quantity of life points in this world is never known with certainty. Life and death overlap each other. The humans then entrusted all their attention to worship under the leadership of sacred entities, popes and cardinals. The holy edicts of the Gods as well as the wise laws that were implemented from the empire itself certainly could not be resisted or would be regarded as r

12 May 2022, 09:48 UTCviews —

Channel name was changed to «ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ»

12 May 2022, 09:32 UTCviews —

Channel name was changed to «It's very painful to walk with thorns stuck in the feet, but these feet must keep walking, to find their life.»

Showing the 12 most recent of 20 posts we hold for @miexture. 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 1 September 2026 — this entry's latest reading, not the date you are reading this.

“Ambivalence.” (@miexture), 8 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/miexture.

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.