海外定向社群渠道落地,按照客户给到的目标关键词,定向挖掘对应圈层社群,梳理渠道资源,客户实测反馈,匹配度符合预期,需求对接高效落地,专注全球海外市场渠道调研,有目标圈层可以直接提需求

Channel
船长引流工作室简介
@UGEKW
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
10,627subscribers
+6,118 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002795303183 |
|---|---|
| Type | Channel |
| Username | @UGEKW |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/UGEKW |
Topic
Marketing & affiliate — 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 12 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 04:21 | 10,627 | -497 |
| 4 Oct 2026, 20:41 | 11,124 | +80 |
| 27 Sept 2026, 07:39 | 11,044 | +4,261 |
| 17 Sept 2026, 18:01 | 6,783 | -843 |
| 13 Sept 2026, 17:38 | 7,626 | -370 |
| 9 Sept 2026, 19:40 | 7,996 | -304 |
| 4 Sept 2026, 15:42 | 8,300 | -189 |
| 1 Sept 2026, 09:15 | 8,489 | -210 |
| 29 Aug 2026, 06:02 | 8,699 | -279 |
| 26 Aug 2026, 10:58 | 8,978 | -236 |
| 23 Aug 2026, 18:26 | 9,214 | -396 |
| 19 Aug 2026, 23:51 | 9,610 | -319 |
| 16 Aug 2026, 22:15 | 9,929 | -155 |
| 15 Aug 2026, 14:15 | 10,084 | +721 |
| 12 Aug 2026, 01:12 | 9,363 | +4,936 |
| 8 Aug 2026, 23:01 | 4,427 | -82 |
| 8 Aug 2026, 03:20 | 4,509 | no change |
| 8 Aug 2026, 03:19 | 4,509 | first reading |
Engagement
14 posts held, back to 26 February 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 23 pages 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 14 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 29s
- Average length
- 29s
Measured directly from 1 video 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.
Reaction mix
48 reactions across 11 posts, in 21 distinct kinds. The most used accounts for 20.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 20.8% | |
| ⚡ | 6 | 12.5% | |
| 🎉 | 5 | 10.4% | |
| 💯 | 5 | 10.4% | |
| 🔥 | 3 | 6.25% | |
| 🎅 | 2 | 4.17% | |
| 🏆 | 2 | 4.17% | |
| 👨💻 | 2 | 4.17% | |
| 🆒 | 1 | 2.08% | |
| 🌭 | 1 | 2.08% | |
| 🍌 | 1 | 2.08% | |
| 🍓 | 1 | 2.08% | |
| 🍾 | 1 | 2.08% | |
| 🎃 | 1 | 2.08% | |
| 🎄 | 1 | 2.08% | |
| 👏 | 1 | 2.08% | |
| 💋 | 1 | 2.08% | |
| 🕊 | 1 | 2.08% | |
| 😁 | 1 | 2.08% | |
| 🤩 | 1 | 2.08% | |
| 1 further kind | 1 | 2.08% |
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 11 of the 14 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 48 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 26 February 2026 to 11 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
⌨⌨⌨引流项目列表⌨⌨⌨ 群发广告套餐 群组强拉/私信套餐 群组/频道 僵尸粉价格 点击字体查看 [私信和群发如何选择] 私信:用户群体精准使用私信一般是 需要进人的交流群或推广项目类适合 用缺点是成本高,价格贵,周期短优 点是短时间内出效果! 群发:群发曝光高,各大担保和赌博 平台都在用打名气的好手子,也适合 一些项目推广。优点是相对于私信价格低周期长,长时间出效果。 群发私信各有优点缺点项目不同效果” 不同因人而异不保效果但100%送达!
❤1🍓1💯1
⌨⌨引流力度效果展示⌨⌨
❤1💯1
新设备已就位,需要群发老板来私
❤1💯1
没有动态的日子里都在专心群发和打磨产品 欢迎老板对比 死号率 群发效果 都是一顶一的强
广告日发百万条,效果如图所示。不同业务每分每秒都在曝光!每一条广告都是精准抵达。不是口嗨/假发那些同行用嘴巴说。
🤣🤣😀😀😀😀😀😀😀😀 🙃长短词,转发频道消息,图片,引用点击跳转频道 防垃圾 自动过验证 自动换群 自动加群 自动退群 💥广告代发全行业覆盖,精准群轰炸 每天人工筛群,让你的广告触及每个活人
❤2
💰广告一发,订单爆炸!群响万遍,黄金万两! 客源如潮水般涌来,生意比火箭还快!全天候待命,稳如泰山 精准引流、横扫千军、马上暴富、顺利上岸!
❤3🎅2🏆2🍌1🍾1🎉1👏1💋1
“您要的不是‘便宜的服务’,而是‘能省心的合作’——我不用低价吸引您,再后期加费用、甩责任,只全程跟进方案执行、效果优化,让您不用花时间反复沟通。”
🎉1🕊1
专业的事,交给专业的人做。选对引流方式。才能让每一分投入都有价值,让流量真正变成“留量”与“销量”
🎉1💯1
🧟♀️部分群发效果展示各大交流群 活跃群 🔈交流群 24小时不停发 【暴力群发】【全天不停】【高效稳定】 【群组匹配】【死号补号】【精准投放】
⚡1🎉1
🧟♀️部分群发效果展示各大交流群 活跃群 🔈交流群 24小时不停发😂😂 【暴力群发】【全天不停】【高效稳定】 【群组匹配】【死号补号】【精准投放】
⚡1🎉1
Showing the 12 most recent of 14 posts we hold for @UGEKW. 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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“船长引流工作室简介” (@UGEKW), 10,627 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/UGEKW.
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.