桜の花びらが舞う
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅

Channel
@be_happy0110
On this record: Growth · Engagement · Posts · Citations · Cite this entry
273subscribers
-8 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001571568591 |
|---|---|
| Type | Channel |
| Username | @be_happy0110 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/be_happy0110 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 03:38 | 273 | -3 |
| 6 Sept 2026, 01:17 | 276 | +1 |
| 28 Aug 2026, 01:38 | 275 | -5 |
| 20 Aug 2026, 02:57 | 280 | -1 |
| 12 Aug 2026, 02:16 | 281 | no change |
| 11 Aug 2026, 13:17 | 281 | first reading |
20 posts held, back to 20 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 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 20 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.
桜の花びらが舞う
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
春桜は雪のよう
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
𝓢𝓹𝓻𝓲𝓷𝓰 𝓓𝓪𝔂
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
十五年等待候鸟
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
𝘚𝘱𝘳𝘪𝘯𝘨𝘭𝘪𝘨𝘩𝘵 𝘞𝘩𝘪𝘴𝘱𝘦𝘳
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
୧ ‧₊˚夏の風に乗って☘︎⋅˚˖
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
ℂ𝕙𝕒𝕡𝕥𝕖𝕣 𝕠𝕗 𝕊𝕡𝕣𝕚𝕟𝕘
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
眼底泛起紫罗兰的薄雾
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
˚.⟡·四季の手引き·๑⁺₊
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
𝘎𝘳𝘢𝘴𝘴𝘭𝘢𝘯𝘥 𝘓𝘶𝘭𝘭𝘢𝘣𝘺
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
༝˚ ⊹.桜が色とりどり. ˖ ♡𓈒
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
✩ ̩͙ ⁺初めての雪 ·̩͙ ⁺.
Signed ゛𝓗𝓾𝓲 𝓨𝓲 ɞ 接 ˚ ⑅
Showing the 12 most recent of 20 posts we hold for @be_happy0110. 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
“难过会消失ಇ” (@be_happy0110), 273 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/be_happy0110.
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.