Telegram RegisterThe public register of Telegram

Channel

Multikda rek 🤍

@multikda_rek

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

11subscribers

+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-1004189765774
TypeChannel
Username@multikda_rek
Created14 June 2026measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/multikda_rek

Growth

117 August 2026 — 11 subscribers12 August 2026 — 11 subscribers7 August 202612 August 2026
2 measurements spanning 5 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 10–12 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 07:0111no change
7 Aug 2026, 18:4411first reading

Engagement

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

Recent posts

14 Jun 2026, 16:03 UTC413 viewsread 12 August 2026

🆕 Kanalga Zayafka qoshamiz! ✅ Status kanallarga ⭐ 100 – 40.000 200 – 80.000 Shop kanallarga ⭐ 100 – 45.000 200 – 90.000 Toza ham qowamz ⭐ Murojaat : ⭐@Reklama_menedjeri 🌟

14 Jun 2026, 16:02 UTC413 views0 reactionsread 12 August 2026

@Multifilimlar_Ozbek_tilida🫀kanali sizga sifatli reklama xizmatini taklif qiladi! 💳 Eslatma ‼️ 1 kun oldin yozing ❗️ 🆕 10/24 80.000 ✅ 🆕 15/24 90.000 ✅ 🆕 20/24 100.000 ✅ 🔺#Murojat qilishda✍️ ✅ Qaysi kanaldan ✅ Qaysi tarifda ✅ Qachonga ekanini aytib keyin murojaat qiling, o'zingizni ham bizni ham vaqtimizni olmang! Maqsadga muvofiq murojaat qilsangiz hammamizga xayrli bo'ladi In Shaa Alloh 🎀 Murojaat : @Rekla

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

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

“Multikda rek 🤍” (@multikda_rek), 11 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/multikda_rek.

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.