3 Feb 2026, 04:34 UTCviews —
᜴𝙢𝙞𝙠𝙠𝙞 𝙥𝙧𝙖𝙘𝙚⏝ pinned a photo
Channel
᜴𝙢𝙞𝙠𝙠𝙞 𝙥𝙧𝙖𝙘𝙚⏝
@mikkiprace
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+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 | -1003755612191 |
|---|---|
| Type | Channel |
| Username | @mikkiprace |
| Created | Between 1 February 2026 and 1 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mikkiprace |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 07:00 | 1 | no change |
| 7 Aug 2026, 18:24 | 1 | first reading |
Engagement
5 posts held, back to 1 February 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 5 posts for this entry, the most recent from 3 February 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 2
- Links
- 2
Lifetime counters from Telegram’s own channel header, read 15 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.
Recent posts
2 Feb 2026, 08:16 UTC34 viewsread 15 August 2026
🥬🥬🥬🥬 🥬🥬🥬 🥬🥬🥬🥬🥬🥬🥬 купить что то из этого можно написав мне в лс- @anex37rrr если бан бот- @mikki_prace_zacaz_bot
1 Feb 2026, 15:47 UTC35 viewsread 15 August 2026
Photo
🥬🥬🥬🥬🥬🥬🥬🥬🥬 🌸🌸🌸🌸🌸🌸🌸🌸 🥬🥬🥬🥬🥬🥬- тык 🥬🥬🥬🥬🥬- тык 🥬🥬🥬🥬 🥬🥬🥬 🥬🥬🥬🥬🥬🥬🥬- тык
1 Feb 2026, 15:42 UTC32 viewsread 15 August 2026
🌸🌸 🐆🐆🐆🐆🐆🐆 🌸🌸 тут вы сможете написать отзыв об одной из услуг🪦
1 Feb 2026, 10:38 UTC282 viewsread 15 August 2026
Photo
🌸🌸🌸🌸🌸🌸🌸🌸 🌸 🌸 🌸☺️🥬🥬🥬🥬: 🌸🌸🌸🌸 🌸сделаю бот на заказ •цена создания бота (с вашей авой и названием) в комплекте идёт сам бот, тгк, чат для администации-15⭐️ •цена создания бота (с моей авой и названием) в комплекте сам бот, тгк, чат для админимтрации-25⭐️ бот анкетница+5⭐️ 🌸оформляю тгк с премимум/без!! (бота/обычный тгк) •1-3 поста- 5⭐️ •больше 3ех постов или весь тгк- 15⭐️ 🌸делаю сигны за 15/25⭐️…
Showing the 5 most recent of 5 posts we hold for @mikkiprace. 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“᜴𝙢𝙞𝙠𝙠𝙞 𝙥𝙧𝙖𝙘𝙚⏝” (@mikkiprace), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/mikkiprace.
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.