Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐢𝐧𝐟𝐨.

Channel

𝐢𝐧𝐟𝐨.

@infomikuu

On this record: Growth · Engagement · Posts · Citations · Cite this entry

41subscribers

+5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002376193536
TypeChannel
Username@infomikuu
Created24 June 2025measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 12 September 2026
On Telegramt.me/infomikuu

Growth

3642396 August 2026 — 36 subscribers7 August 2026 — 37 subscribers10 August 2026 — 37 subscribers21 August 2026 — 39 subscribers28 August 2026 — 42 subscribers4 September 2026 — 41 subscribers416 August 20264 September 2026
6 measurements spanning 29 days, net +5. 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 35–43 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 01:1641-1
28 Aug 2026, 05:1642+3
21 Aug 2026, 03:0239+2
10 Aug 2026, 21:4637no change
7 Aug 2026, 11:4337+1
6 Aug 2026, 12:1936first reading

Engagement

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

Recent posts

5 Apr 2026, 16:41 UTC≈1,780 viewsread 10 August 2026
Photo

. Ი⃪𐑼ִ ׄ welc𖹭me to . . 𝓜𝐢𝐤𝐮 I| 𝗣𝐎𝗥𝗧 🎀 : у других каналов такое красивое оформление !! я хочу такое же :( 🎀 : я не могу найти дизайнера, который работает в нужном мне стиле ⠀ ⎯⎯͟͟ 🗝🗝 ݂ знакомо? ݂ ‹𝟹 я дизайнер под псевдонимом мику . сейчас нахожусь в активном поиске заказов и аудитории. уже имею при себе 45+ хороших отзывов . ૮₍֭𐍷 ᩧ ֑፝֟͡ ֥𐍷₎ᩧ𑇖֥ . 🗝 ⠷ : мои плюсы? 🥹 🥹 O𝟏. ско

24 Jun 2025, 20:00 UTC≈10,400 viewsread 10 August 2026
Photo

❤️ ─ 🎀 : я тоже хочу красивое оформление для своего тгк/флуда/кф! но не знаю где заказать!! 😀😀😀😀😀 вы по адресу! 😀😀😀😀😀 приглашаю вас в 😀😀😀😀😀 ✨свой порт ✨ 🎀 🎇 :: 🦷🦷🦷🦷🦷🦷🦷 я дизайнер со стажем ± год, готовый предоставить вам качественную работу за короткий срок! имею при себе 40+ хороших отзывов . 🎁 мои плюсы? O𝟏. скорость . ⏲️ O𝟐. качество . 💎 03. умение работать в разных стилях . ❤️ 🎀🤍𝖾𝖾𝗒. . 𝖨'𝗆 miku ↳ 🪦

24 Jun 2025, 19:59 UTC≈1,310 viewsread 10 August 2026

🎀 ❤️ 🤍elcome ! 🎀 🔯|. 🕯 o𝐫𝐝𝐞𝐫𝐬 f𝐫𝐨𝐦 . . 𝑚𝑖𝒦𝑢 𝑝𖹭𝑟𝑡 . ׄ𝒩 𝐚𝐯𝐢𝑔ྀི𝐚𝐭𝐢𝑜𝐧 . : 😻 ᴏᴡɴᴇʀ▫️ ᴘʀɪᴄᴇ ▫️ ʀᴇᴠɪᴇᴡs ▫️ 😻ᴘᴏʀᴛꜰᴏʟɪᴏ▫️ᴛᴇᴍᴘʟᴀᴛᴇ 🎀 текстовое оформление 🎀

24 Jun 2025, 19:59 UTC≈1,810 viewsread 10 August 2026
Photo

🌟🌟 ✨ : ❤️ p𝐫𝐢𝐜𝐞 l𝐢𝐬𝐭✨ 😻постоянным клиентам ( 4+ заказов ) полагается скидка – 20℅ . 🎀| аватарка › 100 ₽ 🎀| баннер › 150 ₽ 🎀| постер › 120 ₽ 🎀| вотермарка › 50 ₽ 🎀| прайс на текстовое 🎇﹙ 𝐩.𝐬. работаю только с полной 100% предоплатой. 😻оплату принимаю : русс. рубли - перевод выполняется на карту, только сбер банк. так же, я не несу ответственности за вашу комиссию; номер телефона для сбп не выдается.

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

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

“𝐢𝐧𝐟𝐨.” (@infomikuu), 41 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/infomikuu.

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.