Telegram RegisterThe public register of Telegram
Telegram profile photo for Milpie pimpiee(⁠ ⁠╹⁠▽⁠╹⁠ ⁠)

Channel

Milpie pimpiee(⁠ ⁠╹⁠▽⁠╹⁠ ⁠)

@milpie2

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

12subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003685413092
TypeChannel
Username@milpie2
CreatedBetween 1 December 2025 and 27 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live18 September 2026
Measurements held2
On Telegramt.me/milpie2

Growth

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

Engagement

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

What this channel posts

Photos
29
Videos
4
Links
2

Lifetime counters from Telegram’s own channel header, read 12 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
24s
Average length
24s

Measured directly from 1 video 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.

Reaction mix

230 reactions across 16 posts, in 19 distinct kinds. The most used accounts for 16.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52580505546339519953816.5%
custom 53687857937562054083716.1%
custom 5343889079522068878229.57%
custom 5381801743686323402208.70%
custom 5471901915514150951177.39%
custom 5861566903662680316166.96%
👎146.09%
custom 5316980765815247744125.22%
custom 519945542821113866693.91%
custom 535288148261446998093.91%
custom 538644024394148786393.91%
custom 528738359212772904862.61%
custom 539344976371255249562.61%
custom 526290162141051769252.17%
custom 532560185180503942731.30%
custom 532573945396727336220.87%
🍌20.87%
🤷20.87%
custom 537543624996634227710.435%

Custom emoji. 16 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 are Telegram’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 16 of the 16 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 230 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 27 April 2026 to 10 August 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.

Recent posts

10 Aug 2026, 21:19 UTC10 views13 reactionsread 12 August 2026
Photo

Почему вы подписались на ебучие комментарии,но не на тгк

custom 52580505546339519955custom 53256018518050394273custom 53687857937562054083custom 53257394539672733622

29 Jul 2026, 00:05 UTC22 views16 reactionsread 12 August 2026

Как меня уже заебал этот тритип.То крыло не сходиться,то сх5-сп9-сп4 мистайп,то ещё какая-нибудь хуйня,я щас заплачу😰

custom 52580505546339519956custom 53687857937562054086custom 51994554282111386663custom 53438890795220688781

13 Jul 2026, 11:42 UTC32 views13 reactionsread 12 August 2026
Photo

МОЙ ПЕЛЬМЕНЬ ПЕРВЫЙ

custom 54719019155141509515custom 52580505546339519953custom 53687857937562054083custom 53438890795220688781custom 53818017436863234021

13 Jul 2026, 07:27 UTC31 views18 reactionsread 12 August 2026

Я РЕВУ😐

custom 52580505546339519955custom 53169807658152477444custom 58615669036626803164custom 53687857937562054083custom 53818017436863234022

13 Jul 2026, 07:27 UTC29 views16 reactionsread 12 August 2026
Photo

"—А чё ты белая? Я белая?А ты хули розовая— —Я ЛЕСБИЯ..-" #арт

custom 53934497637125524954custom 58615669036626803164custom 53169807658152477443custom 53438890795220688783custom 53687857937562054082

13 Jul 2026, 06:32 UTC22 views14 reactionsread 12 August 2026

Хвастаюсь своим 12 подписчикам лол

custom 53818017436863234024custom 52580505546339519953custom 53687857937562054083custom 54719019155141509512custom 53438890795220688781custom 53934497637125524951

13 Jul 2026, 06:32 UTC23 views11 reactionsread 12 August 2026
Photo

Я закончила наконец-то 🌟

custom 53169807658152477444custom 53438890795220688782custom 54719019155141509512custom 58615669036626803162custom 51994554282111386661

8 Jul 2026, 11:27 UTC27 views11 reactionsread 12 August 2026

НЕЕТ МОЙ ТГ ПРЕМ Я пошла в очередной раз брать микро кредит

custom 52580505546339519954custom 53438890795220688783custom 58615669036626803162custom 53687857937562054081custom 53818017436863234021

24 Jun 2026, 20:13 UTC37 views14 reactionsread 12 August 2026

Он типа в туалете поняли отмывает кровь,я больше не придумала фон🤩

custom 51994554282111386664custom 52580505546339519954custom 53438890795220688783custom 53169807658152477441custom 53687857937562054081custom 54719019155141509511

24 Jun 2026, 20:12 UTC35 views15 reactionsread 12 August 2026
Photo

Всем привет🤩

custom 52580505546339519954custom 58615669036626803164custom 53687857937562054083custom 53438890795220688782custom 51994554282111386661custom 53818017436863234021

20 Jun 2026, 23:58 UTC34 views11 reactionsread 12 August 2026

На меня наорали и я поменяла реакции🤩

custom 53438890795220688784custom 52580505546339519953custom 53818017436863234022custom 53687857937562054081custom 53934497637125524951

19 Jun 2026, 20:47 UTC40 views14 reactionsread 12 August 2026

Когда-нибудь этот канал будет заполнен рисунками,но не в этом году💝

custom 54719019155141509514👎3custom 53528814826144699803custom 53818017436863234023custom 53438890795220688781

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

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.

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.

“Milpie pimpiee(⁠ ⁠╹⁠▽⁠╹⁠ ⁠)” (@milpie2), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/milpie2.

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.