Channel
@mulkzf
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
80subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003660665375 |
|---|---|
| Type | Channel |
| Username | @mulkzf |
| Description | я червячок |
| Created | 18 December 2025 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mulkzf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 19:02 | 80 | no change |
| 7 Aug 2026, 16:24 | 80 | first reading |
5 posts held, back to 18 December 2025 — the 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 5 posts for this entry, the most recent from 30 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
223 reactions across 4 posts, in 18 distinct kinds. The most used accounts for 11.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5350708912062498083 | 25 | 11.2% | |
| 🍌 | 25 | 11.2% | |
| custom 5373171758524311568 | 20 | 8.97% | |
| custom 5280804655712994143 | 18 | 8.07% | |
| ❤ | 17 | 7.62% | |
| custom 5370809217273859915 | 16 | 7.17% | |
| custom 5262481470529766018 | 14 | 6.28% | |
| custom 5258257159740755785 | 13 | 5.83% | |
| custom 5188602458171023430 | 12 | 5.38% | |
| custom 5474356347589921962 | 12 | 5.38% | |
| custom 5244806112443664103 | 11 | 4.93% | |
| 🎉 | 8 | 3.59% | |
| 💊 | 8 | 3.59% | |
| custom 5278662386155291540 | 7 | 3.14% | |
| custom 5368637402636131323 | 7 | 3.14% | |
| custom 5253481864777208498 | 4 | 1.79% | |
| custom 5264796603931193922 | 3 | 1.35% | |
| custom 5292196270486612404 | 3 | 1.35% |
Custom emoji. 14 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 4 of the 5 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 223reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 18 December 2025 to 30 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
File, posted without a caption
custom 52448061124436641037custom 52786623861552915407custom 53731717585243115685custom 52534818647772084984custom 53708092172738599154custom 52647966039311939223custom 52921962704866124043custom 53686374026361313233
Posted without readable text
custom 528080465571299414310custom 53507089120624980839custom 52582571597407557856custom 52624814705297660186custom 51886024581710234304custom 52448061124436641034custom 53686374026361313234custom 53708092172738599154
🎀🤩Немножко обо мне❓🎀🎀🎀прост факт🎀🎀🤩⭐️⭐️🤩 💤Очень люблю подарки, часто тоже их дарю, считаю это признаком привязанности и любви, ну и не против взаимных подарков 💤Не очень люблю, когда распространяются или пытаются выпытать о моей жизни, если я действительно захочу, я вам расскажу, пожалуйста, не занимайтесь сталкингом и тому подобным. 💤Мне важно, чтобы тебе было комфортно со мной, так что, пожалуйста, говори, если ч…
🍌15❤8💊8custom 53507089120624980838custom 51886024581710234305custom 54743563475899219625custom 52582571597407557854custom 52808046557129941434
🌟🌟🎁🌟° 🌟🌟🌟🌟🌟 🥹🥹🥹ℳı𝗹𝗸︪︩ı𝘇𝗸︪︩ᦅ 29/03🥹🥹🥹❌ 🎀🌟She/he🌟🤍ENFJ🎀🥹🥹 🎀🤍🎀🎁8w9 🤩🎀🎀🤩🎀 🎀сангвиник🤍🤩🤩🤩🎀🎀🍞 🥹🥹 🎀🥹❓🥹🥹💕🥹🍞🍞 😀😀🔤𝐧𝐨𝐧 🦷🥹🥹🥹😻🔵▫️ 🎀 🎀 𝐰𝐡𝐨 𝐚𝐦 𝐈 🤩🥹🥹🤩🎀🎀 🤍 𝐖𝐡𝐨 𝐚𝐦 𝐈 𝐭𝐨 𝐲𝐨𝐮🌸🎀 ❤️🥹🥹 𝐌𝐲 𝐭𝐠𝐤🎁🤍 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🤩 🤩contact @Milkicck..𝖬𝖺𝗒𝖻𝖾 𝗌𝗈𝗆𝖾 𝗉𝖾𝗈𝗉𝗅𝖾 𝖺𝗋𝖾𝗇’𝗍 𝗆𝖾𝖺𝗇𝗍 𝗍𝗈 𝖻𝖾 𝗌𝖺𝗏𝖾𝖽
🍌10❤9🎉8custom 53507089120624980838custom 53731717585243115687custom 52624814705297660185custom 52808046557129941434custom 53708092172738599154
Channel created
Showing the 5 most recent of 5 posts we hold for @mulkzf. 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.
Citation-graph rank — 706,197 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“info Milkis” (@mulkzf), 80 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/mulkzf.
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.