Channel
@jinbiany
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
125,057subscribers
+8,353 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002086501592 |
|---|---|
| Type | Channel |
| Username | @jinbiany |
| Description | 👉聚焦东南亚热点事件、国际新闻、社会动态、华人关注资讯，第一时间更新柬埔寨、斯里兰卡、缅甸、迪拜、马来西亚、泰国、越南、老挝等地区消息 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/jinbiany |
International news — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 89% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 6 other registered channels. They sit inside a group of 9 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @yuenanE/169436 Aug 2026, 13:26 UTC | @jinbiany/5863 · this entry6 Aug 2026, 13:26 UTC | 1.00 | under a minute |
| @jinbiany/5875 · this entry6 Aug 2026, 14:39 UTC | @yuenanE/169576 Aug 2026, 14:39 UTC | 1.00 | under a minute |
| @yuenanE/169596 Aug 2026, 15:20 UTC | @jinbiany/5876 · this entry6 Aug 2026, 15:20 UTC | 1.00 | under a minute |
| @yuenanE/169636 Aug 2026, 15:20 UTC | @jinbiany/5880 · this entry6 Aug 2026, 15:20 UTC | 1.00 | under a minute |
| @jinbiany/5882 · this entry6 Aug 2026, 15:41 UTC | @yuenanE/169656 Aug 2026, 15:41 UTC | 1.00 | under a minute |
| @jinbiany/5994 · this entry7 Aug 2026, 11:58 UTC | @yuenanE/170897 Aug 2026, 11:58 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @yuenanE | 18 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @yuenanE (18–0) |
| @chiguak | 18 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @chiguak (18–0) |
| @xigangz | 18 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @xigangz (18–0) |
| @Bx666x | 18 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @Bx666x (16–2) |
| @yuenanU | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @yuenanU (10–4) |
| @miandianQ | 13 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @miandianQ (11–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 91 of the 91 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 32 comparable posts for this entry, running 6 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 9, the earliest publisher we hold is @miandianQ. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 8 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 21:36 | 125,057 | +52,911 |
| 19 Sept 2026, 02:58 | 72,146 | +6,391 |
| 16 Sept 2026, 15:38 | 65,755 | +49,796 |
| 14 Sept 2026, 21:21 | 15,959 | -385 |
| 13 Sept 2026, 07:21 | 16,344 | -4,493 |
| 11 Sept 2026, 11:19 | 20,837 | -19,331 |
| 8 Sept 2026, 17:57 | 40,168 | -8,029 |
| 5 Sept 2026, 12:55 | 48,197 | -1,836 |
| 3 Sept 2026, 15:18 | 50,033 | -3,520 |
| 2 Sept 2026, 04:44 | 53,553 | -2,720 |
| 1 Sept 2026, 04:04 | 56,273 | -1,328 |
| 31 Aug 2026, 00:55 | 57,601 | -139 |
| 30 Aug 2026, 01:53 | 57,740 | -2,177 |
| 28 Aug 2026, 22:59 | 59,917 | -28 |
| 28 Aug 2026, 00:15 | 59,945 | -1,858 |
| 26 Aug 2026, 22:56 | 61,803 | -2,109 |
| 25 Aug 2026, 22:45 | 63,912 | -1,624 |
| 24 Aug 2026, 21:35 | 65,536 | -2,825 |
| 23 Aug 2026, 07:04 | 68,361 | -14,323 |
| 21 Aug 2026, 15:17 | 82,684 | first reading |
1,225 posts held, back to 6 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 100 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 4 of 642 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 September 2026 |
|---|---|
| Posts held | 1,225 (6 August 2026 – 29 September 2026) |
| Views total | 4,235 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 06:12 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 29 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 359 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.
22 reactions across 22 posts, in 2 distinct kinds. The most used accounts for 86.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 19 | 86.4% | |
| ❤ | 3 | 13.6% |
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 25 of the 1,000 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 15 August 2026 to 29 September 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.
🫥🫥🫥🫥🫥🫥🫥🫥🫥🫥🙂🙂🙂🙂 🍱金贝娱乐 大品牌老牌子 全网广告费每月投入高达500万美金，送“野鸡黑台”一句话，勿伤玩家利益，勿毁博彩信誉。 🍦全球布局 娱乐造富 无惧爆庄 千万任提。 🍦东南亚国家地区不限ip 盘总娱乐首选。 🙂🙂🙂🙂🙂🙂🙂🙂🙂🙂🙂 🙂首存送 复存送 充值笔笔加赠3% 🙂每日以小博大 PG爆奖加赠送彩金 🙂电子百家乐0审核 0风控 包出款 🙂全新代理合作模式55%永久留存 🙂公信力保障、即时开奖、公正透明 🙂储备金以亿为单位 大额秒出无上限 🙂🙂🙂🙂🙂🙂🙂🙂🙂🙂🙂 🥠当无数野鸡网在生灭中挣扎时，金贝始终屹立不倒。这就是我们送给全行业最响亮的耳光！ 🙂🙂🙂🙂🙂🙂🙂🙂🙂 😀😀😀😀😀 @JB03BOT 🙂🙂🙂🙂🙂 @jinbei07 🙂🙂🙂🙂🙂 @jinbeidaili 🙂🙂🙂🙂🙂 @JBzhaoshang 🙂🙂🙂🙂🙂 jinbei2000.com
波贝洪水中惊现大鳄鱼，当地警方和民众合力将其抓获 9月29日上午，波贝市中央市场分区4号村一带正遭遇洪水，当地警方及相关部门联合民众，成功抓获一条体型很大的鳄鱼。被抓获后，鳄鱼已被转移到安全地点暂时安置，等待后续处理。 波贝市政府提醒民众提高警惕，尤其不要让孩子下洪水中玩水，以免发生意外，同时也要小心洪水中可能出现的蛇等危险动物。 PS：嘎嘣脆，鸡肉味🤣 频道独家广告赞助商 ——————————————— 😎😎😎😎😎 😎😎😎😎储备金3亿U 大胆创 上押担保300万美金 ——————————————— 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @idid
#网友爆料：刘春清，谢敏红，温世玉，大家一定要注意这3个人，遇见请绕道。 事情发生在9月25日下午，刘春清打视频给我，说他在巴基斯坦打野做欧美空降诈骗，感觉被骗了，抱怨项目不好，称自己已从公司跑出来，身上没钱，想来我朋友的公司。确认情况后，我朋友给他购买了从巴基斯坦飞泰国的机票。由于他曾去过几次柬埔寨，担心在泰国出境会遭遣返，我朋友再三确认安全后，花了一千多U给他保关，并花5000多人民币购买了巴基斯坦飞泰国的往返机票。他说没钱没衣服穿，我朋友又给他转了3300人民币。 接下来更可气的是，他拉了一个群，说有两个老乡现在老挝打野做国内资金盘诈骗，也想和他一起过来。这两个人我以前不认识，分别是谢敏红和温世玉。在群里再三确认后，他们发了护照在群里。由于他们两人也有柬埔寨的记录，我们花了2800给他们买了老挝飞泰国的往返机票，同时花了2000多U给他们保关。说他们没有生活费，我朋友又给他们转了2500人民币。 接着最可气的事情发生…
#老挝资讯：沙湾拿吉省警方捣毁一个网络犯罪团伙及一个买卖卡痛叶团伙 9月28日，老挝沙湾拿吉省公安部门联合凯山·丰威汉市公安部门以及省人民检察院工作人员，对涉嫌从事网络犯罪活动以及买卖卡痛叶的两个地点进行搜查。 第一处地点： 警方搜查了位于沙湾拿吉省凯山·丰威汉市蓬沙旺南村的一处出租住宅。搜查过程中，警方发现15名嫌疑人员，其中包括14名中国籍人员和1名老挝籍人员。 现场还发现了涉嫌用于违法活动的设备，包括台式电脑38台、智能手机41部。 第二处地点： 警方搜查了位于沙湾拿吉省凯山·丰威汉市沙南赛村的一处出租排屋。据悉，该处涉及一个涉嫌从事卡痛叶及“DI”药水买卖的团伙。搜查过程中发现2名嫌疑人员，其中1人为女性，两人均为老挝籍。 现场查获的物品包括：卡痛叶3大袋，另有134小袋；“DI”药水22,963瓶；汽车1辆。 目前，沙湾拿吉省公安指挥部门仍在继续进行调查、审讯，以查明相关违法人员，并依法追究其法律责任。…
#群友投稿：今天凌晨马来西亚柔佛新山，扫黄抓了两车小姐，又一批女朋友没了😭😭😭 频道独家广告赞助商 ——————————————— 😎😎😎😎😎 😎😎😎😎储备金3亿U 大胆创 上押担保300万美金 ——————————————— 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @idid
看来之前的富人查税风波是真的了，彭博今天发了篇信息量巨大的专题。 里面写道了不少，本轮针对富人的税务追查案例，力度空前。甚至海底捞的联创也被查了，其中香港是这轮征税的重点目标之一，还提到了后续即将可能到来的遗产税。 频道独家广告赞助商 ——————————————— 😎😎😎😎😎 😎😎😎😎储备金3亿U 大胆创 上押担保300万美金 ——————————————— 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @idid
😀😀😀😀😀😀😀😀😀😀😀😀😀😀 😀铂莱娱乐 8年老品牌 全网广告费每月投入高达500万美金，送“野鸡黑台”一句话，勿伤玩家利益，勿毁博彩信誉。 😃全球布局，娱乐造富，无惧爆庄，千万任提！ 😀😀😀😀😀😀😀😀😀😀 😀首存送 复存送 充值笔笔加赠3% 😀每日以小博大 PG爆奖加赠送彩金 😀电子百家乐0审核 0风控 包出款 😀全新代理合作模式55%永久留存 😀公信力保障、即时开奖、公正透明 😃东南亚国家地区不限ip 盘总大哥娱乐首选。 😀😀😀😀😀😀😀😀😀😀 😀当无数野鸡网在生灭中挣扎时，铂莱始终屹立不倒。这就是我们送给全行业最响亮的耳光！ 😀😀😀😀😀😀😀😀😀😀 🟢🟢😀😄: @BL01bot 😀😀😀😀: @BLKF0 😀😀😀😀: @bolaidaili 😀😀😀😀: @BLzhaoshang 😀😀😀😀: bolai4000.com 😀😀😀柬埔寨地区部分用户访问不了主域名，请访问
柬埔寨和美国联合执法 焚毁逾800吨假冒烟草制品 柬埔寨当局与美国执法官员合作，成功焚毁了从非法工厂查获的800多吨假冒烟草制品。 美驻柬大使馆昨天证实，此次行动由柬内政部与美方联合开展，旨在打击跨国犯罪网络及非法烟草交易。 美方强调，国际合作对加强边境执法、保护知识产权及阻止违禁品流入全球市场至关重要。此次清缴意在保障公众健康、维护环保标准，并打击不公平竞争，以保护合法投资者在柬权益。 频道独家广告赞助商 ——————————————— 😎😎😎😎😎 😎😎😎😎储备金3亿U 大胆创 上押担保300万美金 ——————————————— 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @idid
#群友求助：西港凯蒂国际黑赌场/平哥丧尽天良/出马洗码卡号999-11 赌场总经理和平哥出马团队狼狈为奸。总经理答应给钱，最后出尔反尔。西港第一黑赌场/出马公司。 平哥原来带领一群25仔在亚多利出马，后面被曝光多次，亚多利老板把他轰出去了。现在搬到凯蒂继续出马坑害中国人，里面筹码牌手都是亚多利带过去的。牌手会出老千/抽2张牌。被骗过去出马的中国人赢钱退不到钱。输钱被打的半死，实在还不出钱来的就贩卖到缅甸亚太妙瓦底这些大型黑公司上班。每天过着惨无人睹的日子。没有业绩的就会被卖器官心脏。 凯蒂已经被曝光多次了，依然无视柬埔寨法律法规，还在坑害中国人。据说里面现在关押着很多中国人不给吃饭不给睡觉。天天折磨。酒店楼上有很多诈骗公司，他们白天睡觉，晚上开工骗人。有做色料，资金盘。欧美盘。 凯迪出马负责人：平哥。平哥此人最大恶极，专门在凯迪赌场出马坑害中国人，长期混迹在柬埔寨夜场，长期贩卖人口，打骂中国人。此人天天吸DU。 开迪出…
9月28日，彭博社引述知情人士报道，中国税务部门已组建特别小组，追踪富豪并向其征税，部分小组甚至专门针对一名亿万富翁。 频道独家广告赞助商 ——————————————— 😎😎😎😎😎 😎😎😎😎储备金3亿U 大胆创 上押担保300万美金 ——————————————— 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @idid
#小姐姐投稿：由于本人深受打击和影响，婚内出轨、证据确凿 我老公去柬埔寨出差与一盘口的财务越南已婚女人，有老公孩子还跟我老公在一起，每天私信发很多照片每天视频电话，一直骚扰。严重影响我的情绪！我实在没有办法，第一次发这种帖子。 频道独家广告赞助商 ——————————————— 😎😎😎😎😎 😎😎😎😎储备金3亿U 大胆创 上押担保300万美金 ——————————————— 👉东南亚大事件: @kk888 👉东南亚吃瓜群: @kk999 👉东南亚素材库: @zhaopian 👉投稿澄清爆料: @idid
迪拜王储晒出的一张车票照片，把迪拜居民的火车期待拉满了 迪拜王储在Snapchat上晒了张火车票，39迪拉姆，从迪拜坐到阿布扎比。这个动作本身，比任何官方预告都更有说服力。 阿联酋副总理兼国防部长、迪拜王储谢赫·哈姆丹·本·穆罕默德·本·拉希德·阿勒马克图姆在Snapchat上分享了他的阿提哈德铁路车票，展示了在迪拜客运服务正式启动前，往返于两个酋长国之间的行程。 车票显示为“舒适级”选项，票价39迪拉姆起。 他发帖的时机很有意思。9月30日，普通乘客就要第一次登上这条从迪拜出发的新线路了。对阿联酋国家客运铁路网络来说，这是一个重要的里程碑。 谢赫·哈姆丹的车票显示的是迪拜与阿布扎比之间的行程。随着9月30日迪拜客运服务启动日期的临近，人们对这条线路的期待也在升温。 这项新服务将连接位于迪拜Jumeirah Golf Estates的 Al Yalayis 站与阿布扎比的穆罕默德·本·扎耶德城站。阿提哈德铁路已重新开…
Showing the 12 most recent of 1,225 posts we hold for @jinbiany. 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 12 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 16 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 3 seed channels' Telegram-generated recommendation lists 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“东南亚大事件 柬埔寨大事件 柬埔寨新闻” (@jinbiany), 125,057 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/jinbiany.
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.