Telegram RegisterThe public register of Telegram

Channel

daily wlw x mlm sekai

@mlmwlwsekai

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

2subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001626089666
TypeChannel
Username@mlmwlwsekai
Descriptionдейлик, посвященный млм и влв секай пейрингам cr:: 425migfy
Created5 August 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/mlmwlwsekai

Growth

27 August 2026 — 2 subscribers14 August 2026 — 2 subscribers7 August 202614 August 2026
2 measurements spanning 6 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”. The vertical axis spans 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 03:172no change
7 Aug 2026, 19:552first reading

Engagement

19 posts held, back to 5 August 2023the 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 19 posts for this entry, the most recent from 9 August 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
26
Links
3

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

Reaction mix

29 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 41.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓1241.4%
💘827.6%
413.8%
💋310.3%
❤‍🔥26.90%

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 12 of the 19 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 29reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 5 August 2023 to 9 August 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

9 Aug 2023, 17:25 UTC93 views5 reactionsread 14 August 2026
Photo

. . ° #ichisaki #fanart ⤷ cr :: ao_porigon twt . . •

💘5

8 Aug 2023, 11:06 UTC99 views3 reactionsread 14 August 2026
Photo

. . ° #mafuena #fanart ⤷ cr :: nozmy_ twt . . •

❤‍🔥1🍓1💋1

8 Aug 2023, 10:12 UTC89 views4 reactionsread 14 August 2026
Photo

. . ° #ruikasa #fanart ⤷ cr :: nyelu0416 twt . . •

🍓3❤‍🔥1

7 Aug 2023, 17:03 UTC82 views1 reactionsread 14 August 2026
Forwarded from @DailyNeneKasaPhoto

ㅤㅤㅤ [ НАВИГАЦИЯ ] ㅤВсем привет! Это канал посвящен пейрингу НенеКаса/ТсукаНене из игры ColorfulStage Ft. Hatsune Miku, либо же Секай. На канале иногда будет публиковаться контент только с Нене или Тсукасой. Правила канала. Дни канала: Базовый, хэйтеры редких пейрингов,фанаты ТойКас/ТойСаки,поддержка стран агрессоров,деление квиров на софт/хард. Хэштеги: #nenekasa – основной хэштег #nene

🍓1

7 Aug 2023, 16:23 UTC60 views1 reactionsread 14 August 2026
Photo

‼️навигатор по каналу‼️ всем привет, добро пожаловать в группу - daily akikoha, посвещённый пейрингу акито шинономэ и кохане азусаве из группы "Vivid Bad Squad" и игры "project sekai" × теги #akito - два #kohane - главных #akikoha - пупса #an - ан шираиши, участница vbs #toya - тойя аояги, участник vbs #others - другие персонажи #art - фанарты #official - официальные арты, новости и т.д #edit - эдиты #3dmv - с

💘1

7 Aug 2023, 13:55 UTC72 views2 reactionsread 14 August 2026
Photo

. . ° #akirui #fanart ⤷ cr :: jizhu68846825 twt . . •

🍓2

7 Aug 2023, 10:29 UTC71 views3 reactionsread 14 August 2026
Photo

. . ° #ichisaki #fanart ⤷ cr :: ichisakifiles twt . . •

🍓3

7 Aug 2023, 10:24 UTC67 views2 reactionsread 14 August 2026
Photo

. . ° #emunene #fanart ⤷ cr :: aie_rtk twt . . •

🍓2

6 Aug 2023, 12:43 UTC80 views1 reactionsread 14 August 2026
Photo

. . ° #mizurui #fanart ⤷ cr :: jealswo twt . . •

1

6 Aug 2023, 12:41 UTC73 viewsread 14 August 2026
Photo

. . ° #kanaena #fanart ⤷ cr :: cocov__ twt . . •

5 Aug 2023, 22:02 UTC89 views3 reactionsread 14 August 2026
Photo

. . ° #akikasa #fanart ⤷ cr :: mojitochan228 twt . . •

💋21

5 Aug 2023, 19:43 UTC69 viewsread 14 August 2026
Photo

✩ ⋆ ° . ✩ ⋆ ° . ✩ ⋆ ° . ✩ ( ( 🕊 ) приветствую!! хочешь рассказать о своих хэдканонах на персонажей? поделиться своим творчеством по секаю? высказать свое честное мнение, касающееся игры или ее фандома? поделиться впечатлениями от новых карт и ивента? показать результаты круток или прохождения песен? если ответ хотя бы на один вопрос был положительным, то как насчёт того, чтобы з

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

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

“daily wlw x mlm sekai” (@mlmwlwsekai), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/mlmwlwsekai.

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.