Telegram RegisterThe public register of Telegram
Telegram profile photo for milkyway🎀

Channel

milkyway🎀

@milkywway52

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

71subscribers

+3 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-1002050938633
TypeChannel
Username@milkywway52
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/milkywway52

Growth

687169.57 August 2026 — 68 subscribers10 August 2026 — 68 subscribers14 August 2026 — 70 subscribers22 August 2026 — 71 subscribers5 September 2026 — 70 subscribers13 September 2026 — 71 subscribers7 August 202613 September 2026
6 measurements spanning 37 days, net +3. 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 68–71 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 15:2271+1
5 Sept 2026, 14:5870-1
22 Aug 2026, 18:2771+1
14 Aug 2026, 11:1970+2
10 Aug 2026, 01:0068no change
7 Aug 2026, 16:0868first reading

Engagement

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

What this channel posts

Video runtime
21s
Average length
7s

Measured directly from 3 videos 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

65 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 50.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52964221747084848543350.8%
custom 52965497953667170521929.2%
custom 53574471445192552901320.0%

Custom emoji. Every row above is a 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 3 of the 3 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 65 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 3 most recent posts we hold, published 1 July 2026 to 21 July 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

21 Jul 2026, 19:11 UTC53 views19 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 529642217470848485412custom 52965497953667170527

Signed мила

21 Jul 2026, 19:10 UTC50 views15 reactionsread 10 August 2026
Photo

все как родное🙏🏻🙏🏻

custom 529654979536671705212custom 52964221747084848543

Signed мила

1 Jul 2026, 16:24 UTC103 views31 reactionsread 10 August 2026
Video

выпускной🏫

custom 529642217470848485418custom 535744714451925529013

Signed мила

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

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

“milkyway🎀” (@milkywway52), 71 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/milkywway52.

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.