10 Jul 2026, 10:14 UTC57 viewsread 10 August 2026
Photo
До 13 июля на все расклады действуют скидки -20%🫰🏽 Запись в личку: @alekssadmi Первым двум готовность в ближайший час!
Channel
ПРАЙС РАСКЛАДЫ @aleksa.dmi 🫀
@aleksaprise
On this record: Growth · Engagement · Posts · Citations · Cite this entry
35subscribers
-1 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 | -1002054085308 |
|---|---|
| Type | Channel |
| Username | @aleksaprise |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 10 September 2026 |
| On Telegram | t.me/aleksaprise |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 03:26 | 35 | -2 |
| 15 Aug 2026, 19:13 | 37 | +1 |
| 10 Aug 2026, 22:15 | 36 | no change |
| 7 Aug 2026, 17:29 | 36 | first reading |
Engagement
6 posts held, back to 14 March 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 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 6 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
27 May 2026, 14:05 UTC208 viewsread 10 August 2026
Photo
Новый расклад на лето 🌞 Заказать тут @alekssadmi Отличная возможность подготовиться к лету, узнав, что же вас ждет и на что лучше обратить внимание, а также построить планы исходя из прогноза 😋
23 Mar 2026, 06:37 UTC219 viewsread 10 August 2026
Forwarded from @aleksataroPhoto
Всем привет❤️ Создала группу в вк, а то не пойми что с телегой, на всякий случай подпишитесь, буду туда тоже выкладывать что-нибудь интересное про таро https://vk.ru/aleksatarot
24 Dec 2025, 09:10 UTC556 viewsread 10 August 2026
Photo
😍РАСКЛАДЫ НА СЕБЯ И ДРУГОЕ запись: @alekssadmi
24 Dec 2025, 09:04 UTC471 viewsread 10 August 2026
Photo
💋РАСКЛАДЫ НА ЛИЧНУЮ ЖИЗНЬ 2 часть 1 часть раскладов запись: @alekssadmi
14 Mar 2025, 09:04 UTC≈1,010 viewsread 10 August 2026
Photo
🕯️РАСКЛАДЫ НА БУДУЩЕЕ запись: @alekssadmi
Showing the 6 most recent of 6 posts we hold for @aleksaprise. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“ПРАЙС РАСКЛАДЫ @aleksa.dmi 🫀” (@aleksaprise), 35 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/aleksaprise.
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.