18 Jul 2024, 18:55 UTC13 viewsread 27 August 2026
ೀ ⋮ ➤ список союзов катии 1 — 2 —
Signed катии💘
Channel
𝘤𝘰𝘻𝘺 𝘮𝘪𝘭𝘢𝘨𝘭𝘺↯
@milagly
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001901603227 |
|---|---|
| Type | Channel |
| Username | @milagly |
| Description | топи владелец — @katushhkp начало — 31 апреля 2023 |
| Created | Between 1 March 2023 and 30 November 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/milagly |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 11:45 | 2 | no change |
| 27 Aug 2026, 11:30 | 2 | first reading |
Engagement
2 posts held, back to 18 July 2024 — 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 2 posts for this entry, the most recent from 18 July 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Videos
- 1
Lifetime counters from Telegram’s own channel header, read 27 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
- 1s
- Average length
- 1s
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.
Recent posts
18 Jul 2024, 18:55 UTC13 viewsread 27 August 2026
Video
——``⇝RULES FOR UNIONS ╰➤мой юз — @katushhkp ‹‹⊹･взаимная подписка обязательна в любом случае, отписка следящего — разрыв ╰➤ не участвуем в чистках, нас строго автоматом ‹‹⊹･посты мы делаем обязательно и всегда ╰➤ все важное у нас в закрепе! ‹‹⊹･при смене ссылки-названия-канала-закрытия — сообщать следящему за вами в лс ‹‹⊹･теги — #milagly #милагли #milaglyRP ‹‹⊹･юз канала — @milagly
Signed катии💘
Showing the 2 most recent of 2 posts we hold for @milagly. 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“𝘤𝘰𝘻𝘺 𝘮𝘪𝘭𝘢𝘨𝘭𝘺↯” (@milagly), 2 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/milagly.
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.