纯马来私人抖音 (可以换绑香港出货) 自己可以找小弟实名0违规
❤1
Signed A椰子 【@f4888 八年号商】

Channel
@yezi19819
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
8,271subscribers
-379 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001618739792 |
|---|---|
| Type | Channel |
| Username | @yezi19819 |
| Description | 频主 @f4888 椰子 @yezi1982 自助机器人 @yezi1981_bot 各种微信 公众号 企业微信 微博 抖音钉钉号 小红书 快手QQ WS号 FB ins KK企业 台湾line 出售 合作愉快 ❤️2026椰总集团品牌值得信奈 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/yezi19819 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 19:59 | 8,271 | -5 |
| 5 Nov 2026, 16:56 | 8,276 | -11 |
| 2 Nov 2026, 21:55 | 8,287 | -12 |
| 31 Oct 2026, 00:49 | 8,299 | -21 |
| 27 Oct 2026, 15:50 | 8,320 | -9 |
| 25 Oct 2026, 00:54 | 8,329 | -10 |
| 22 Oct 2026, 07:21 | 8,339 | -30 |
| 18 Oct 2026, 16:40 | 8,369 | -14 |
| 15 Oct 2026, 21:16 | 8,383 | -11 |
| 12 Oct 2026, 17:31 | 8,394 | -13 |
| 6 Oct 2026, 13:17 | 8,407 | -20 |
| 29 Sept 2026, 15:02 | 8,427 | -60 |
| 19 Sept 2026, 02:58 | 8,487 | -30 |
| 14 Sept 2026, 10:20 | 8,517 | -54 |
| 11 Sept 2026, 06:38 | 8,571 | -99 |
| 6 Sept 2026, 04:39 | 8,670 | +6 |
| 2 Sept 2026, 01:25 | 8,664 | +13 |
| 30 Aug 2026, 10:13 | 8,651 | +2 |
| 27 Aug 2026, 12:25 | 8,649 | -1 |
| 26 Aug 2026, 19:25 | 8,650 | first reading |
52 posts held, back to 22 August 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 16 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. It is computed over the 1 of 27 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 52 (22 August 2026 – 9 November 2026) |
| Views total | 7,073 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 12:46 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.
Lifetime counters from Telegram’s own channel header, read 9 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 5 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.
4 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 100.0% |
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 5 of the 52 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 52 most recent posts we hold, published 22 August 2026 to 9 November 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.
Telegram’s own ‘edited’ marker: 3 of 30 posts held from the last 30 days (10.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
纯马来私人抖音 (可以换绑香港出货) 自己可以找小弟实名0违规
❤1
Signed A椰子 【@f4888 八年号商】
🟥椰子抖音号商集团📣【韩国Kakao台湾line日本line商品发布群】 pinned «马来西亚🇲🇾私人三年非解 质量天花板,价格地板砖 无视ip 国内网也可以»
马来西亚🇲🇾私人三年非解 质量天花板,价格地板砖 无视ip 国内网也可以
Signed A椰子 【@f4888 八年号商】
马来换绑香港微信🇭🇰最近好用
Signed A椰子 【@f4888 八年号商】
📱📱快手 直登国卡/美卡(金牛)报白 安卓备份包(国卡)! 苹果爱思包(国卡)! 均有现货秒发 售后:24小时掉线 5天找回 5天激活
Signed A椰子 【@f4888 八年号商】
美卡全实名千粉回流号0违规 还有10几个
Signed A椰子 【@f4888 八年号商】
私人港年全实名 到货一批!
Signed A椰子 【@f4888 八年号商】
🉑进群号来了 肯尼亚半年已恢复 邮箱登录可立马进群不死 接粉加人不死 邮箱登录 无视国外IP 除国内网络 价格不贵 也可爱思包 包过验证 包1u卡 售后:包十分钟不操作死
Signed A椰子 【@f4888 八年号商】
大量现货,苹果12备份 开播 不开播都有 蓝v系列 苹果12备份 1.店铺栏 2.新版蓝 3.商家认证蓝 4.抖音来客 新老都有,提前说好要新的还是老的
Signed A椰子 【@f4888 八年号商】
看上的带价格来聊 卖东西的 粉有价值 全实名 0违规 51.7万粉
Signed A椰子 【@f4888 八年号商】
日本官方line价格 日本脱棒line价格 日本带绑line价格 泰国line价格 香港line价格 台湾脱绑 台湾1-2年以上带购物记录 日本企业line过7天,价格根据当天 韩国半年一年line 各国TG号 1-10年 各种额度礼品卡 代付 代付 车队通畅 椰子📱📱📱📱📱 @f4888
Signed A椰子 【@f4888 八年号商】
香港已经准备好半年了
Signed A椰子 【@f4888 八年号商】
Showing the 12 most recent of 52 posts we hold for @yezi19819. 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.
@yezi19819 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.
We recorded 1 post on @yezi19819 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“🟥椰子抖音号商集团📣【韩国Kakao台湾line日本line商品发布群】” (@yezi19819), 8,271 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/yezi19819.
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.