Channel
@tsikadatea
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
995subscribers
+44 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002021521881 |
|---|---|
| Type | Channel |
| Username | @tsikadatea |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/tsikadatea |
Ecommerce storefront — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 97% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 04:39 | 995 | +10 |
| 6 Sept 2026, 10:01 | 985 | +12 |
| 28 Aug 2026, 14:25 | 973 | +4 |
| 21 Aug 2026, 07:58 | 969 | +20 |
| 13 Aug 2026, 11:23 | 949 | -1 |
| 7 Aug 2026, 11:28 | 950 | -1 |
| 6 Aug 2026, 18:30 | 951 | no change |
| 6 Aug 2026, 18:20 | 951 | first reading |
5 posts held, back to 4 August 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
20 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 35.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5384171779654696614 | 7 | 35.0% | |
| custom 5244874655826733409 | 5 | 25.0% | |
| custom 5291868598841657359 | 5 | 25.0% | |
| custom 5264965224347231444 | 2 | 10.0% | |
| 💔 | 1 | 5.00% |
Custom emoji. 4 of the rows above are 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 5 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 20 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 4 August 2026 to 6 August 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.
🙂🙂🙂🙂 🙂 🙂🙂🙂 Шен Пуэр 89 Лао Мань Э 2018г Во вкусе: • Сухофрукты • Мягкое дерево • Пряности В аромате: • Яблоки • Сладкие Цветы • Капля мёда Яркий, мягкий чай Почти без горчинки ______ Стоимость: 89р за 1 грамм Заказать с доставкой: @tsikada_tea 89955965329 #ассортимент #шенпуэр #новинки
custom 52448746558267334091custom 52649652243472314441custom 52918685988416573591
🙂🙂🙂🙂🙂🙂🙂 🙂🙂🙂🙂🙂🙂🙂 • Исинский чайник Разбитая крышка, скол на носике и ножке Большая сетка трещин, Круговая скоба под крышкой и штифты • Пиала с котиком И фактурное золото Небольшой скол на теле Предметы уже у своих владельцев🍃 #кинцуги
custom 53841717796546966145custom 52448746558267334092custom 52918685988416573592
На встречу по Пекинской опере осталось 3 места🍃
💔1
Так прошла встреча по основам Гадания в Древнем Китае И вот, что мы узнали: - Почему летом нужно есть курицу, иначе случится землетрясение - Почему чиновник виноват, что тигры съели людей - Как по жукам, которые съели урожай, понять, какие чиновники плохо работают в древней канцелярии - Почему варваров было 4 вида, а не 5 и не 6 - Как варвару поменять своё сердце на человеческое У варваров сердца птиц и зверей,…
custom 53841717796546966142custom 52448746558267334091custom 52918685988416573591
Уже запланировали следующую встречу по Гаданию В Древнем Китае 13 сентября, воскресенье, 19:00 Что вы узнаете: - Как поймать вора - Автоматическое письмо без электричества - Гадания на костях дракона И где их купить, но это не точно - Какие ещё были гадания - Про гадания по Фэн-Шую - И ещё много другого интересного __________________ Стоимость сейчас - 1000р Записаться: @tsikada_tea 89955965329 #мероприяти…
custom 52448746558267334091custom 52649652243472314441custom 52918685988416573591
Showing the 5 most recent of 5 posts we hold for @tsikadatea. 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 3 registered channels — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Цикада 茶 Чайный клуб” (@tsikadatea), 995 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/tsikadatea.
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.