Channel
@taronex
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002190061931 |
|---|---|
| Type | Channel |
| Username | @taronex |
| Created | 16 June 2024 — measured — dated from the channel’s first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 4 times, most recently 9 September 2026 |
| On Telegram | t.me/taronex |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 17:24 | 3 | no change |
| 15 Aug 2026, 03:02 | 3 | first reading |
5 posts held, back to 16 June 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 5 posts for this entry, the most recent from 16 June 2024. An engagement rate over an empty window would be a number about nothing.
6 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 100.0% |
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 4 of the 5 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 16 June 2024 to 16 June 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
В чому мінус розкладів на відповідь так/ні? Звісно такі розклади можливі, але рекомендувати їх робити я не можу, так само не беру їх на розклад, і допомагаю переформулювати питання. Звісно виникає запитання «Чому?», а відповідь проста як світ. З карт можна взяти набагато більше інформації, і це спрощення системи просто напросто немає ніякого сенсу.
❤1
Чи варто трактувати перевернуті карти? Дуже популярне серед тарологів питання, на яке і досі немає однозначної відповіді. Найголовніше тут, не засуджувати людей за їх спосіб трактування, допоки їх розклади працюють вірно, засуджувати немає за що. Проте, якщо брати до уваги мою думку, як людини що досить довго знаходиться в цій сфері, перевернуті карти я не трактую. І на це є одна досить примітивна причина. Символіка …
❤2
Хочу почати займатись, з якої колоди розпочати? На це питання є однозначна відповідь — Таро Уейта Це колода з класичною символікою, що є найкращим вибором для новачків, і універсальною для будь якого запитання Також неймовірним плюсом є кількість літератури в напрямку вивчення данної колоди, інформації несчисленно, що робить вивчення набагато зручніше і цікавіше.
❤1
ПРАЙС Питання - 20 грн Думки, почуття, дії - 50 грн Писати @crstlcln Розклади більше ніж на три питання зі знижкою, залежно від кількості запитань та складності
❤2
Channel created
Showing the 5 most recent of 5 posts we hold for @taronex. 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.
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.
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“ТАРО | РОЗКЛАД ✨” (@taronex), 3 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/taronex.
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.