Channel
@yunlinsale
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
7subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001568594304 |
|---|---|
| Type | Channel |
| Username | @yunlinsale |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 12 September 2026 |
| On Telegram | t.me/yunlinsale |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 10:12 | 7 | -1 |
| 12 Aug 2026, 15:17 | 8 | no change |
| 7 Aug 2026, 01:46 | 8 | first reading |
5 posts held, back to 4 August 2024 — 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 23 August 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
地区: 马卡蒂 小区:Paseo De Roces 2栋 30楼 规格:一室一厅 售价: 3.5M 净价 付款方式：26平方， 价格可谈，联华超市楼上，靠近The Oriental Place 微信:Azurezufang 接待客服飞机：@Yunlindichan88 @lilyofthevalley088 #Paseo De Roces SHORE 房源 SHELL 房源 马卡蒂房源 BGC 房源 帕赛小区房源 帕拉尼亚克房源 房源出售及别墅
地区:帕赛 小区:SHORE2 1栋 3楼 规格:一室一厅 售价: 3.4M 净价 28平方 ，产证已有 随时可过户，捡漏的老板抓紧了 微信:Azurezufang 接待客服飞机： @Yunlindichan8888 @lilyofthevalley088 #SHORE2 #Tower1 SHORE 房源 SHELL 房源 马卡蒂房源 BGC 房源 帕赛小区房源 帕拉尼亚克房源 房源出售及别墅
地区:帕拉尼亚克 小区: Coastal Luxury 2栋 18楼 规格:二室一厅 售价: 14M 净价 93平方 ， 已付全款 等待产证，房东急甩， 价格可谈 金湾临近PITX电车站，临近SSK 大楼，附近更是靠近okada 赌场 微信:Azurezufang 接待客服飞机： @Yunlindichan8888 @lilyofthevalley088 #Coastal Luxury Residence （御景金湾） SHORE 房源 SHELL 房源 马卡蒂房源 BGC 房源 帕赛小区房源 帕拉尼亚克房源 房源出售及别墅
地区:帕拉尼亚克 小区: bayshore2 C栋 9楼 规格:一室一厅 售价: 11.5M 净价 60平方 ， 带停车位 已付全款 等待产证，房东急甩， 价格可谈 靠近okada 赌场，已有租户。买到即可收益 微信:Azurezufang 接待客服飞机： @Yunlindichan8888 @lilyofthevalley088 #BAYSHORE2 SHORE 房源 SHELL 房源 马卡蒂房源 BGC 房源 帕赛小区房源 帕拉尼亚克房源 房源出售及别墅
地区:帕赛 小区:SHORE D栋 12楼 规格:一室一厅 售价: 3.35M 净价 27平方 ，有银行贷款，捡漏的老板们 抓紧了 微信:Azurezufang 接待客服飞机： @Yunlindichan8888 @lilyofthevalley088 #SHORE #TowerD SHORE 房源 SHELL 房源 马卡蒂房源 BGC 房源 帕赛小区房源 帕拉尼亚克房源 房源出售及别墅
Showing the 5 most recent of 5 posts we hold for @yunlinsale. 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.
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.
Named by 7 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.
@yunlinsale named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“雲琳地产出售房屋房源” (@yunlinsale), 7 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/yunlinsale.
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.