Telegram RegisterThe public register of Telegram
Telegram profile photo for Archive KZM

Channel

Archive KZM

@MikxoVideo

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

9subscribers

+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-1002041654257
TypeChannel
Username@MikxoVideo
Descriptionbellong to: @STARS_IDOLS
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live31 August 2026
Measurements held2
On Telegramt.me/MikxoVideo

Growth

931 Aug 2026, 05:00 — 9 subscribers31 Aug 2026, 05:15 — 9 subscribers31 Aug 2026, 05:0031 Aug 2026, 05:15
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 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 05:159no change
31 Aug 2026, 05:009first reading

Engagement

20 posts held, back to 31 July 2024the 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 20 October 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3
Videos
39

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

Video runtime
3m 34s
Average length
21s

Measured directly from 10 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

20 Oct 2024, 12:09 UTC137 viewsread 31 August 2026
Video

CR: @Yaexmikxo tag: @Penyelundupp @KIBUTSIJJ @Miechikatsu @Evenesoent @Puilchrify @esclante @blownies mamamtuh cabe cabean

18 Oct 2024, 02:08 UTC173 viewsread 31 August 2026
Video

cr: @Yaexmikxo tag @Penyelundupp @KIBUTSIJJ @esclante @Puilchrify @blownies @Evenesoent @Miechikatsu []

12 Oct 2024, 06:23 UTC53 viewsread 31 August 2026
Video

@Lsamsh @CREDTH @sRAHARA @cigrttaftsexx @Wanyderer @pGloire @dpudingg @velldrad @thCutestgirl @andourarae @iSweetGirliex @Rafa_yell @Cornerstoine @aShuyi @Yaexmikxo @Perfectjly @esclante @KIBUTSIJJ @sLaviender @blownies @soshlrohoshina @Ryoaka @Sucxit @NavieerTrovy @Kokuzhibo @GoEunhyuek @Narpidana @lsangpuitis @Chucklews @cjgarettesx @oLautanBiru @wRionkenzo @Geogravicc @elegantact @Sollitudes @inicedar @mualaxni

12 Oct 2024, 06:23 UTC36 viewsread 31 August 2026
Video

@Lsamsh @CREDTH @sRAHARA @cigrttaftsexx @Wanyderer @pGloire @dpudingg @velldrad @thCutestgirl @andourarae @iSweetGirliex @Rafa_yell @Cornerstoine @aShuyi @Yaexmikxo @Perfectjly @esclante @KIBUTSIJJ @sLaviender @blownies @soshlrohoshina @Ryoaka @Sucxit @NavieerTrovy @Kokuzhibo @GoEunhyuek @Narpidana @lsangpuitis @Chucklews @cjgarettesx @oLautanBiru @wRionkenzo @Geogravicc @elegantact @Sollitudes @inicedar @mualaxni

6 Oct 2024, 13:58 UTC153 viewsread 31 August 2026
Video

CR: @yaexmikxo Tag: @myokara @Pradiptazean @blownies @dpudingg @Waguirii

22 Sept 2024, 16:09 UTC77 viewsread 31 August 2026
Video

CR: @uDamselette tag: @Nagkanohara @kiehtagawa @yFuruyaRei @primadojnna @thCutestgirl @Narpidana @blownies @sLaviender @CvntQ @Kokuzhibo

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

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

“Archive KZM” (@MikxoVideo), 9 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/MikxoVideo.

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.