Telegram RegisterThe public register of Telegram
Telegram profile photo for 若柠🍋🏠别墅

Channel

若柠🍋🏠别墅

@ruoni8881

Has discussion group

On this record: Topic · Previous handles · Growth · Engagement · Citations · Cite this entry

1,989subscribers

+1,013 since we began measuring on 27 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003670289843
TypeChannel
Username@ruonj888q
Description联系 @ruoni038 双向 @ruoni368_bot 群组 https://t.me/ruonj012
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 October 2026
Last confirmed live3 November 2026
Measurements held11
On Telegramt.me/ruoni8881

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 12 October 2026 and assigned it the closest of 31 fixed categories, at 93% 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 the other topics.

Previous handles

@ruoni8881 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@ruoni8881
held 3 November 2026 – 3 November 2026

Growth

12,2921,146.527 September 2026 — 976 subscribers4 October 2026 — 1,248 subscribers4 October 2026 — 1,248 subscribers11 October 2026 — 1,376 subscribers14 October 2026 — 1,414 subscribers18 October 2026 — 1,470 subscribers21 October 2026 — 2,292 subscribers24 October 2026 — 1 subscribers30 October 2026 — 3 subscribers3 November 2026 — 1,989 subscribers3 November 2026 — 1,989 subscribers1,98927 September 20263 November 2026
11 measurements spanning 37 days, net +1,013. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 04:031,989no change
3 Nov 2026, 03:471,989+1,986
30 Oct 2026, 14:573+2
24 Oct 2026, 01:201-2,291
21 Oct 2026, 11:272,292+822
18 Oct 2026, 00:011,470+56
14 Oct 2026, 13:401,414+38
11 Oct 2026, 11:591,376+128
4 Oct 2026, 18:241,248no change
4 Oct 2026, 18:151,248+272
27 Sept 2026, 06:48976first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Cite this entry

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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“若柠🍋🏠别墅” (@ruoni8881), 1,989 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/ruoni8881.

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.