кошечка нашлась, спасибо большое всем! 🙏🏻
custom 534803466785550849578custom 545868703987876104426

Channel
@teawithsunny
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
2,585subscribers
-143 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001913755539 |
|---|---|
| Type | Channel |
| Username | @teawithsunny |
| Created | 16 July 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/teawithsunny |
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 |
|---|---|---|
| 17 Sept 2026, 14:15 | 2,585 | -17 |
| 13 Sept 2026, 23:01 | 2,602 | -14 |
| 10 Sept 2026, 06:17 | 2,616 | -17 |
| 4 Sept 2026, 15:00 | 2,633 | -10 |
| 1 Sept 2026, 05:12 | 2,643 | -8 |
| 29 Aug 2026, 06:45 | 2,651 | -6 |
| 26 Aug 2026, 12:48 | 2,657 | -13 |
| 23 Aug 2026, 04:47 | 2,670 | -13 |
| 19 Aug 2026, 13:57 | 2,683 | -6 |
| 16 Aug 2026, 21:45 | 2,689 | -7 |
| 13 Aug 2026, 23:34 | 2,696 | -15 |
| 10 Aug 2026, 21:04 | 2,711 | -17 |
| 7 Aug 2026, 20:22 | 2,728 | no change |
| 7 Aug 2026, 20:02 | 2,728 | first reading |
15 posts held, back to 15 June 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 15 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 8 videos 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.
2,675 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 56.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5348034667855508495 | 1,521 | 56.9% | |
| custom 5458687039878761044 | 1,154 | 43.1% |
Custom emoji. Every row above is a 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 15 of the 15 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 2,675 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 15 June 2026 to 5 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @teawithsunny. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 15 most recent posts we hold for this entry, published 15 June 2026 to 5 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
кошечка нашлась, спасибо большое всем! 🙏🏻
custom 534803466785550849578custom 545868703987876104426
москва, метро раменки 🙏🏻
custom 545868703987876104478custom 534803466785550849535
«с малыхой 👍🏻»
custom 5458687039878761044169custom 534803466785550849592
мой глазик заметил алмазик
custom 5348034667855508495134custom 545868703987876104469
hoon`s ✶ weverse update ( 성훈 ) : с днём рождения, сону-я!🎂
custom 5348034667855508495130custom 545868703987876104464
RIDE OR DIE M/V
custom 545868703987876104473custom 534803466785550849531
oh…
custom 5348034667855508495117custom 545868703987876104459
teasing is their love language 😭 hoon: кто-то хочет покататься со мной на байках? won: он разве не один? hoon: их два, но один для сону sun: сону?? won: детский типа? hoon: да (дырявый рот роняет еду) sun: это карма
custom 5348034667855508495129custom 545868703987876104462
oh i feel kinda … 🤩
custom 5458687039878761044127custom 534803466785550849583
чонвон взялся пожарить рыбу, о которой сонхун думает с прошлого выпуска, и кошечку сону очевидно она тоже привлекла 😒 won: это сонхуна? hoon: а? это мое hoon: я не ем пасту sun: можно я кусочек возьму? hoon: нет, я купил это sun: мог бы и поделиться в целом, сонхуна по прежнему ничего не останавливает дразнить сону 🤷
custom 545868703987876104494custom 534803466785550849563
sun: отойдите won: они нам помогают в конце концов sun: о да, спасибо большое 😒 hoon: мясо горит sun: серьезно, хватит hoon: в любом случае, я не буду есть томатную пасту sun: тогда почему ты так много говоришь? 😒 ok, bro?! что такого сделал сонхун, что сону за этот выпуск ему даже слова сказать не даёт 😭 я ребёнок развода…
custom 5348034667855508495109custom 545868703987876104460
hoon: сону пожарь это sun: … нет все таки терпение сону не резиновое, и, кажется, оно закончилось..😑
custom 5348034667855508495112custom 545868703987876104475
Showing the 12 most recent of 15 posts we hold for @teawithsunny. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“sunsunverse !” (@teawithsunny), 2,585 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/teawithsunny.
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.