Telegram RegisterThe public register of Telegram
Telegram profile photo for 集团频道📍🇱🇰🇹🇭🇦🇪🇲🇾🇻🇳

Channel

集团频道📍🇱🇰🇹🇭🇦🇪🇲🇾🇻🇳

@DESMOND0713

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Declared links · Cite this entry

310subscribers

+40 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001183129002
TypeChannel
Username@DESMOND0713
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/DESMOND0713

Topic

Job listings — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@DADESMOND1/129330 Jun 2026, 08:23 UTC@DESMOND0713/852 · this entry30 Jun 2026, 08:25 UTC0.9872 seconds
@DADESMOND1/130419 Jul 2026, 09:14 UTC@DESMOND0713/862 · this entry19 Jul 2026, 09:21 UTC0.987 minutes
@DADESMOND1/12951 Jul 2026, 09:43 UTC@DESMOND0713/854 · this entry1 Jul 2026, 09:47 UTC0.984 minutes
@DADESMOND1/13113 Aug 2026, 15:26 UTC@DESMOND0713/867 · this entry3 Aug 2026, 15:27 UTC0.98under a minute
@DADESMOND1/12997 Jul 2026, 14:12 UTC@DESMOND0713/857 · this entry7 Jul 2026, 14:13 UTC0.98under a minute
@DADESMOND1/13134 Aug 2026, 14:25 UTC@DESMOND0713/868 · this entry4 Aug 2026, 14:26 UTC0.97under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@DADESMOND18 (8/8 hand-verifiable sample passed)0.9772 seconds@DADESMOND1 (8–0)

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. None of the 8 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 22 June 2026 to 4 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @DADESMOND1. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

2703743228 August 2026 — 270 subscribers8 August 2026 — 270 subscribers21 August 2026 — 288 subscribers28 August 2026 — 299 subscribers4 September 2026 — 309 subscribers12 September 2026 — 315 subscribers30 September 2026 — 374 subscribers10 October 2026 — 343 subscribers17 October 2026 — 332 subscribers25 October 2026 — 331 subscribers31 October 2026 — 330 subscribers8 November 2026 — 321 subscribers17 November 2026 — 310 subscribers3108 August 202617 November 2026
13 measurements spanning 101 days, net +40. 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”. The vertical axis spans 254–390 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 12:36310-11
8 Nov 2026, 22:06321-9
31 Oct 2026, 19:39330-1
25 Oct 2026, 00:36331-1
17 Oct 2026, 03:38332-11
10 Oct 2026, 00:02343-31
30 Sept 2026, 13:21374+59
12 Sept 2026, 06:57315+6
4 Sept 2026, 07:39309+10
28 Aug 2026, 18:38299+11
21 Aug 2026, 21:27288+18
8 Aug 2026, 08:49270no change
8 Aug 2026, 03:16270first reading

Engagement

20 posts held, back to 22 June 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 of the 20 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 22 June 2026 to 4 August 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.

Recent posts

4 Aug 2026, 14:26 UTC29 viewsread 8 August 2026
Photo

岗位:数据分析专员(2名) 🇳🇬🇲🇽😕☺️🙃🙃😇🙃 薪资待遇:2080U-2500U+绩效+餐补一天15U 工作时间:🫵🫵🫵🫵🫵 性别:优先女 年龄:20-35 国籍:中国籍,马来西亚籍,越南籍(非河南、山东,福建均可) 学历:大专 语言要求:中文读、听、写佳 工作地点:🤓😗🤓 😘😗🤓😗 1.大专及以上学历优先;中文沟通流畅,听读写无障碍 2.熟练使用 Excel,掌握函数、数据透视表、Power Query 等常用工具 3.具备良好的数据分析能力、逻辑思维能力及数据敏感度,能够独立完成数据分析并形成结论 4. 熟悉数据分析方法,能够从数据中发现问题并提出可执行的优化建议 5. 工作认真细致,责任心强,具备良好的沟通协调能力和团队合作意识。 6. 具备较强的学习能力,能够快速理解业务逻辑及数据口径 😊😎😘🙂‍↔️ 1.负责数据的收集、整理、统计及分析,建立周度及月度数据报表 2.根据业务需求,独立完成活动分析、用户分析及专题…

3 Aug 2026, 15:27 UTC28 viewsread 8 August 2026
Photo

岗位:统筹专员(2名) ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 薪资待遇:2080U-2500U+绩效+餐补一天15U 工作时间:🫵🫵🫵🫵🫵 性别:优先女 年龄:20-35 国籍:中国籍,马来西亚籍,越南籍 (非河南、山东,福建均可) 学历:大专 语言要求:中文 读、听、写佳 工作地点:🤓😗🤓 😘😗🤓😗 1. 大专及以上学历优先;中文沟通流畅,听读写无障碍 2. 具备优秀的文字表达能力和文案功底,能够独立撰写各类汇报材料、分析报告及项目方案 3. 熟练使用 PowerPoint,具备良好的内容策划、逻辑梳理及版面设计能力,能够独立完成汇报PPT 4. 具备较强的信息提炼和总结归纳能力,能够快速抓住重点,并将复杂信息进行结构化表达 5. 熟练使用 Word、Excel、PowerPoint 等办公软件,具备基础数据整理及分析能力。 6. 具备良好的沟通协调能力、执行力及抗压能力,能够同时推进多个专项工作。 7. 工作细致认真,责任心强…

3 Aug 2026, 14:47 UTC36 views1 reactionsread 8 August 2026
Photo

岗位:运营策略专员(3名) ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 薪资待遇:1670U-2500U+绩效+餐补一天15u 工作时间:🫵🫵🫵🫵🫵 性别:优先女 年龄:20-35 国籍:中国籍,马来西亚籍(非河南、山东,福建均可) 性别:大专 语言要求:中文 读、听、写佳 工作地点:🤓😗🤓 😘😗🤓😗 1. 大专及以上学历优先;2年以上BC行业经验;1年以上运营、风控、项目管理相关工作经验;中文沟通流畅,听读写无障碍 2. 具备较强的逻辑思维能力、业务分析能力及策略规划能力,能够独立完成运营策略研究及方案输出。 3. 具备良好的数据敏感度,能够结合数据分析发现问题并提出可落地的策略建议。 4. 熟练使用 Excel、Word、PowerPoint 等办公软件,具备基础数据分析能力。 5. 具备优秀的沟通协调能力,能够与运营、产品、数据等团队高效协作。 6. 学习能力强,责任心强,具备较强的执行力及抗压能力。 😊😎😘🙂‍↔️ 1. 负责…

❤1

27 Jul 2026, 10:48 UTC84 viewsread 8 August 2026
Photo

🇳🇬🇲🇽😕☺️🙃☺️😚 岗位:红利专员(3名)💛 薪资待遇:1390U-1940U+绩效+餐补一天15U 工作时间:🫵🫵🫵🫵🫵三班倒 性别:不限 年龄:21-35 国籍:不限(非河南、山东,福建均可) 学历:大专 语言要求:中文 读、听、写佳 工作地点:🤓😗🤓 😘😗🤓😗 1、能以中文进行流利表达,具备良好的听说读写能力。 2、需要有一年以上红利工作经验。 3、具备一定的体育相关知识与经验,能够熟练使用表格基础函数。 4、具备丰富行业经验及较强数据统计能力,熟练使用表格公式进行数据分析者优先考虑。 😊😎😘🙂‍↔️ 1、 审核优惠活动,审核礼品资格,派发彩金跟进礼品派发前后问题等; 2、 追踪与跟进各部门反馈的问题,直到解决为止; 3、 对接各部门反馈的问题并回复与解决(必须及时回复) 🙈🙈🙈🙈㊗: @Win0713 🎁 🙈🙈🙈🙈㊗: @DADESMOND1 🎁

27 Jul 2026, 10:30 UTC45 viewsread 8 August 2026
Photo

岗位:运营专员(10名) 薪资待遇:1390U-1940U+绩效+餐补一天15U 工作时间:9小时(月休4)三班倒 性别:不限 年龄:21-35 国籍:中国籍(非河南、山东,福建均可) 性别:大专 语言要求:中文,读、听、写佳 工作地点:泰国 岗位需求: 1、有一年以上运营工作经验(包含其他同类型或者工作内容相似的岗位) 2、了解运营工作,熟悉基本的B端对接、平台运营、内容配置、后台操作使用等运营业务内容者优先; 3、有跨中心或跨部门对接运营工作事项的经验优先; 4、具备上进心与积极的工作态度,拥有较强的责任感,认真踏实; 5、有基本电脑操作常识与经验,打字速度不低于60字/分钟; 6、熟悉使用excel、ppt等办公软件。 7、必须接受跟随至第三国 岗位职责: 1、对接公司各个对内部门,协助完成线上反馈各类问题的处理及跟踪; 2、三方场馆的日常事务对接,建立及维护关系,沟通、处理、跟踪场馆日常出现的各类问题,处理场馆维护…

24 Jul 2026, 13:01 UTC66 viewsread 8 August 2026
Photo

🇲🇱🇸🇷🇸🇾🇧🇱🇰🇳🇸🇪 岗位:薪酬专员🇹🇬 性别:不限 年龄:不限 国籍:不限/泰籍优先 性别:本科 薪资待遇:12-15K+绩效+餐补 工作时间:14:00-21:00 工作地点:🇬🇳🇲🇹🇲🇹 🇵🇳 主要是有推广部门助理经验接触过做薪资提成数据这样,偶尔也要出外勤,语言方面除了中文,英语或者泰语能沟通就行。 😘😗🤓😗 1、熟悉使用各类办公软件,如:excel,word等,需要能够熟悉使用各种函数 2、需要能够长期任职的人员,心态要平和,稳重,对数字要有一定敏感性 3、人员工作会对接外部,需要有良好的表述能力及思维能力,可自行判断处理一些问题 在职期间发生任何问题需即使报备反馈部门,不允许出现先斩后奏的情况。 😊😎😘🙂‍↔️ 对接各部门,对接核算薪资数据,整理分析薪酬数据,整理薪酬相关操作流程制度。 🇰🇷🇹🇼🇪🇸🇱🇨㊗ @Win0713 🎁 🇮🇴🇪🇺🇨🇺㊗ @DADESMOND1 🎁

19 Jul 2026, 09:21 UTC110 viewsread 8 August 2026
Photo

岗位:java架构师(1名)🙃🇲🇽 🇸🇨🇴🇲🇵🇭☺️🙃🙂☺️😊 薪资待遇:50K-80K+绩效+餐补一天15U 工作时间:10小时(10:00-20:00) 性别:男 年龄:40以下 国籍:外籍(不要缅甸/伊斯兰教/泰国籍) 工作地点:🤓😗🤓 😘😗🤓😗 1. 精通Java语言,善于解决各种Java的性能问题 2. 精通Java社区的主流框架,并且具备定制和扩展能力 3. 具备优秀的系统分析和设计能力,能提前针对项目情况做出合理的规划和设计 4. 具备良好的工具文化,能利用各类工具或者优化使用方式提升和改善团队效率 5. 有比较丰富的敏捷开发实践,对敏捷开发实践有比较深刻的认知者优先 6. 熟练掌握K8S、Service Mesh等云原生技术,有实操经验者优先 7. 持续学习,乐于分享,善于思考,善于总结归纳沉淀,具备优秀的分析和解决问题能力; 8. 乐观随和,具备优秀的团队协作精神,善于和各种背景的人合作 9. 有强烈的责任心…

17 Jul 2026, 08:25 UTC59 viewsread 8 August 2026
Photo

岗位:报告编辑 1名🇵🇳🇵🇳 ☺️🙃🙃😇🙃🙃🇲🇽 薪资待遇:转正15k左右"转正后绩效范围1K-3K,具体面议 工作时间:🫵🫵🫵🫵🫵9:00-18:00 性别:不限 年龄:25-38岁 国籍:中国籍 学历:本科以上,理科优先 语言要求:英语6级 工作时间:🇮🇩🇮🇹🇭🇳 * 需要外宿,专员外宿标准1800迪。提供公司餐*需要附上中英文简历 😘😗🤓😗 1、本科及研究生以上学历,理科优先,不分男女; 2、学习或工作经历涉及以下行业,数据统计与分析、调研、咨询、金融等; 3、3年以上从业经验 ; 4、入职时间要求:尽快入职。 😊😎😘🙂‍↔️ 1、领导小组成员完成客户及上级的调研任务需求,涉及到调研项目的主导分析、调研流程的规划、调研过程中的跟进指导、最终调研报告的审核产出; 2、代表团队负责与上级、客户的对接; 3、负责部门日常工作的规划,对产出的结果负责。 4、为公司相关产业发展提供信息支持和决策支持,主要方向为:博彩类、支付类…

15 Jul 2026, 05:59 UTC69 viewsread 8 August 2026
Photo

岗位:DBA工程师 (6名)🇵🇳 ☺️🙃🙂☺️😊🙃🇲🇽 性别:不限 年龄:21-35(中国籍)21-30(外籍) 国籍:中国籍(福建籍,新疆籍除外) 外籍(东南亚地区)不招印度,菲籍,泰籍,华侨为主 语言要求:中/英文(必须会一种) 学历:大专及以上 薪资待遇:面议 工作时间:🫵🫵🫵🫵🫵 工作地点:🇮🇩🇮🇹🇭🇳 😘😗🤓😗 1 有Linux 操作经验,或计算机专业毕业,热爱IT行业 2 有oracle sql server mysql TIDB 等任意一种数据库维护经验 3 有AI操作经验优先,有自动化维护数据库经验者 😊😎😘🙂‍↔️ 1 负责各类型数据库日常维护,管理 2 排查服务故障,分析和解决疑难问题 3 监控,告警,漏洞,调优,负载均衡 🇰🇷🇹🇼🇪🇸🇱🇨㊗ @Win0713 🎁 🇮🇴🇪🇺🇨🇺㊗ @DADESMOND1 🎁

14 Jul 2026, 13:45 UTC66 viewsread 8 August 2026
Photo

岗位:产品运营 1名 ☺️🙃☺️😚🙃🇲🇽 薪资待遇:2000U-3000U+绩效+餐补一天15U 工作时间:11小时 性别:不限 年龄:32岁以内 国籍:中国籍 不要东北地区 性别:不限 语言需求:中文 工作地点:🤓😗🤓 😘😗🤓😗 有行业经验,必须对体育赛事敏感。且至少懂盘口。不要小白,不要无护照。 懂AI、体育产品、AI分析类,副体育直播 具备管理团队和扩招。 🇰🇷🇹🇼🇪🇸🇱🇨㊗ @Win0713 🎁 🇮🇴🇪🇺🇨🇺㊗ @DADESMOND1 🎁

12 Jul 2026, 11:23 UTC65 viewsread 8 August 2026
Photo

🇲🇹🇸🇱🇵🇭🇧🇧😘🙂😞🤨🇰🇬🇳🇴 岗位:运营专员(负责棋牌)7名 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 薪资待遇:1250U-2000U+绩效+餐补一天15U 工作时间:🫵🫵🫵🫵🫵三班倒 性别:不限 年龄:21-35岁 国籍:中国,台湾,马来西亚(非福建、河南、山东均可) 学历:不限 语言需求:中文 工作地点:🤓😗🤓 😘😗🤓😗 曾於BC產業/線上遊戲產業之運營崗位工作1以上年的資歷,對於產品的跨部門溝通協作、版本控制、活動規劃、數據分析、競品分析有一定經驗和實績表現,熟悉棋牌品類產品者優先。 😊😎😘🙂‍↔️ 版本進度掌控、版本測試驗收、活動策劃、數據分析、競品調研分析等 🙈🙈🙈🙈㊗: @Win0713 🎁 🙈🙈🙈🙈㊗: @DADESMOND1 🎁

7 Jul 2026, 14:13 UTC73 viewsread 8 August 2026
Photo

岗位:高级UI设计师(2名) 🇳🇬🇲🇽😕☺️🙃🙂☺️😊 国籍:中国籍 年龄:35岁以内 性别:男 学历:大专以上 薪资待遇:底薪4200-5200USD加绩效加餐补一天15U 工作地点:🇬🇳🇲🇹🇲🇹 😘😗🤓😗 1、5年以上设计经验;拥有设计团队管理经验、有大型直播项目的上线项目者优先考虑(附带作品或链接); 2、有Codex、Claude、Midjourney、ComfyUI、Lovart等AI智能体/AI工具用到工作流者优先; 3、熟悉iOS,Android,web设计规范,熟练搭建figma变量系统、组件库; 4、具备沟通协作能力,配合团队执行工作任务、态度端正、积极主动、有责任心,具有一定的抗压能力; 5、学习能力强,具备优秀的审美能力、扎实的视觉与交互设计功底,能驾驭多种UI设计风格表现手法、独立输出高质量方案; 6、大专以上学历,美术/艺术设计相关专业。 😊😎😘🙂‍↔️ 1、负责产品视觉、界面(UI)与数据可视化设…

Showing the 12 most recent of 20 posts we hold for @DESMOND0713. 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.

Mentions

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.

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.

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

“集团频道📍🇱🇰🇹🇭🇦🇪🇲🇾🇻🇳” (@DESMOND0713), 310 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/DESMOND0713.

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.