Channel
@cuptea
On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Telegram's recommendations · Cite this entry
11,197subscribers
-134 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001059870740 |
|---|---|
| Type | Channel |
| Username | @cuptea |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/cuptea |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 36% 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 |
|---|---|---|
| 5 Sept 2026, 12:40 | 11,197 | -12 |
| 3 Sept 2026, 15:41 | 11,209 | -10 |
| 2 Sept 2026, 08:28 | 11,219 | -4 |
| 1 Sept 2026, 07:27 | 11,223 | -10 |
| 31 Aug 2026, 04:45 | 11,233 | -8 |
| 30 Aug 2026, 06:43 | 11,241 | -6 |
| 29 Aug 2026, 06:14 | 11,247 | +2 |
| 28 Aug 2026, 07:18 | 11,245 | -9 |
| 27 Aug 2026, 09:27 | 11,254 | -3 |
| 26 Aug 2026, 07:02 | 11,257 | -3 |
| 24 Aug 2026, 08:59 | 11,260 | -10 |
| 22 Aug 2026, 13:07 | 11,270 | -9 |
| 21 Aug 2026, 01:52 | 11,279 | -2 |
| 20 Aug 2026, 01:06 | 11,281 | -7 |
| 18 Aug 2026, 21:55 | 11,288 | -6 |
| 17 Aug 2026, 21:26 | 11,294 | -2 |
| 16 Aug 2026, 22:34 | 11,296 | -4 |
| 15 Aug 2026, 17:28 | 11,300 | -6 |
| 14 Aug 2026, 02:35 | 11,306 | -3 |
| 13 Aug 2026, 00:04 | 11,309 | first reading |
31 posts held, back to 5 July 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 42 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 31 (5 July 2026 – 29 August 2026) |
| Views total | 14,224 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 01:43 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
"ربما لم يكن أجدادنا أقل حزنًا منا، لكنهم كانوا أقرب إلى الأشياء التي تُهدّئ القلب: طريقٌ طويل، وجبلٌ صامت، وسماءٌ واسعة، وجداول ماء، ومزرعة حنونة، كانوا يعرفون بالفطرة أن بعض الأسئلة لا تحتاج جوابًا، بل تحتاج نُزهة".
مدري .. قولي انت ايش؟ @cup1teabot
من يهتم بغرق شخص وحيد؟
منذ وقت طويل لم أعد اسأل السماء شيئاً، ومع ذلك ظلّت يداي ممدودتين. -أنطونيو بورشيا
"كل الذين فهموا الحياة جيدوا، اختاروا البساطة والهدوء وقلة الظهور".
مالذي يجعلك سعيد في هذه اللحظة؟ @cup1teabot
هناك شيء في نفوسنا حزين قد يختفي، ولا يبين لكنه مكنون شيء غريب .. غامض .. حنون!*
ماذا يحتاج الإنسان ليشعر فعلا أن حياته لم تذهب سدى؟ @cup1teabot
"يا الله أعد إليّ نفسي أو خذها كاملة فإني تعبتُ من أن أكون نصف نجاة ونصف هاوية".
"كم مرة عليّ أن أوصد هذا الباب؟ الباب الذي ليس له قفل، الباب المفتوح على الندم".
في الوقت الذي تفرغت فيه لنفسي شعرت بالحزن.
"لا شيء يستحق ان تمد يديك لانقاذه، اترك الاشياء تاخذ نصيبها من الإرتطام".
Showing the 12 most recent of 31 posts we hold for @cuptea. 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.
@cuptea edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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 1 seed channel's Telegram-generated recommendation list 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“كوب شاي.” (@cuptea), 11,197 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/cuptea.
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.