Telegram RegisterThe public register of Telegram
Telegram profile photo for 斯里兰卡 空运快递 @LK123

Channel

斯里兰卡 空运快递 @LK123

@LKwuliu

2 usernames

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

7,916subscribers

-3,081 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001737214397
TypeChannel
Usernames@lk123 @LKwuliu
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/LKwuliu

Growth

7,91610,9979,456.57 August 2026 — 10,997 subscribers7 August 2026 — 10,997 subscribers8 August 2026 — 10,977 subscribers8 August 2026 — 10,977 subscribers9 August 2026 — 10,969 subscribers9 August 2026 — 10,969 subscribers10 August 2026 — 10,784 subscribers10 August 2026 — 10,618 subscribers11 August 2026 — 10,416 subscribers11 August 2026 — 10,301 subscribers12 August 2026 — 10,135 subscribers12 August 2026 — 9,948 subscribers13 August 2026 — 9,641 subscribers15 August 2026 — 8,289 subscribers16 August 2026 — 7,916 subscribers7 August 202616 August 2026
15 measurements spanning 9 days, net -3,081. 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 7,454–11,459 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 18:077,916-373
15 Aug 2026, 16:448,289-1,352
13 Aug 2026, 04:589,641-307
12 Aug 2026, 13:349,948-187
12 Aug 2026, 02:1410,135-166
11 Aug 2026, 16:1510,301-115
11 Aug 2026, 05:0110,416-202
10 Aug 2026, 13:0310,618-166
10 Aug 2026, 06:2010,784-185
9 Aug 2026, 13:0110,969no change
9 Aug 2026, 09:5210,969-8
8 Aug 2026, 12:4410,977no change
8 Aug 2026, 10:3610,977-20
7 Aug 2026, 19:3110,997no change
7 Aug 2026, 19:1810,997first reading

Engagement

19 posts held, back to 15 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
9.75%
avg views ÷ 7,916 subscribers
Avg views / post
772
17 posts measured
Reaction rate
0.327%
reactions ÷ views · ER floor
Posts in window
17
of 19 held

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 5 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held19 (15 July 202614 August 2026)
Views total13,125
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 08:15 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.

Reaction mix

7 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍342.9%
💩228.6%
114.3%
🔥114.3%

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 6 of the 19 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 15 July 2026 to 14 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

14 Aug 2026, 06:25 UTC88 views3 reactionsread 15 August 2026

📢 盲盒售出通知 感谢大家的关注与支持! 🎁 本次盲盒已 售出,感谢各位的关注与参与。 后续如有新的盲盒上架,我们会第一时间发布通知,敬请关注。 感谢支持!🙏

👍2🔥1

14 Aug 2026, 04:51 UTC92 viewsread 15 August 2026

📢 快递盲盒|行李箱处理通知 现有 1个行李箱 作为快递盲盒处理。 🧳 数量: 1个 ⚖️ 重量: 约12KG 🎁 内容: 快递盲盒,具体物品随机 💰 价格: 私聊咨询 📍 处理方式: 先到先得 ⚠️ 温馨提示: 盲盒内容随机,确认后不接受因个人喜好产生的退换,请确认可以接受后再参与。 📩 有兴趣的直接私聊,仅此1箱! 免费送货上门 📲 唯一客服:@LKtiantian 🤖 24小时快递助手:@YX168bot

13 Aug 2026, 05:15 UTC114 views2 reactionsread 15 August 2026
Photo

✈️ 8月20日|曼谷 → 越南 → 兰卡 🇹🇭 曼谷 → 🇻🇳 越南 → 🇱🇰 斯里兰卡 📦 需要代购、带货或帮忙带东西? 现在即可联系客服登记! 🛍️ 代购商品 📦 帮忙带东西 🎁 购买当地特色商品 ⏰ 名额有限,建议提前登记,方便安排 📲 唯一客服:@LKtiantian 🤖 24小时快递助手:@YX168bot

👍1💩1

12 Aug 2026, 12:50 UTC115 viewsread 15 August 2026
Photo

🚨 空运快递重要通知|受台风天气影响,部分航班及运输时效或将延迟 📢 尊敬的客户: 受近期台风及恶劣天气影响,部分航班可能出现延误、调整或货物配载顺延情况,进而影响中国 🇨🇳 → 斯里兰卡 🇱🇰 空运快递的运输时效。 📌 温馨提示: • 航班及货物运输将根据实际天气情况动态调整 • 部分包裹预计会出现一定程度的时效延迟 • 已发出的货物请耐心等待,我们会持续跟进运输进度 • 天气恢复正常后,将尽快安排后续航班及派送 🙏 由此带来的不便,敬请谅解。 我们将持续关注台风及航班动态,全力保障货物安全,并尽快恢复正常运输时效。 📦 感谢大家的理解与支持!

5 Aug 2026, 18:11 UTC248 views2 reactionsread 15 August 2026
Photo

📢 商家专属福利通知 为更好地服务各位合作商家,即日起,凡通过我们物流发货的商家,均可享受送货上门及代收服务。 ✅ 减少商家取货时间成本 ✅ 配送更省心、更高效 ✅ 提升客户收货体验 ✅ 提供代收服务,资金/货物处理更灵活 ✅ 长期合作商家可享稳定配送支持 我们希望通过更完善的物流服务,帮助商家把更多时间投入到经营中,让发货更简单、生意更轻松。 📦 适用对象: 通过本渠道发货的合作商家。 📩 如需安排送货上门或代收服务,请提前联系客服确认配送信息。 一站式物流配送,用心服务每一位商家。 📲 唯一客服联系方式: @LKtiantian 🤖 24小时快递助手 @YX168bot

1💩1

4 Aug 2026, 02:51 UTC271 views0 reactionsread 15 August 2026
Photo

🚬 中国 → 斯里兰卡 香烟空运线路已恢复正常发货 即日起,中国发往斯里兰卡的香烟空运业务正常收货、正常发运。 ✅ 正常收货 ✅ 正常安排航班 ✅ 正常清关配送 ✅ 时效稳定,支持长期发货 有发货需求的客户可提前联系客服预约发货,按要求打包寄出即可。 温馨提示: 请务必提前咨询最新寄件要求及数量限制,以便安排最快航班,避免影响时效。 📩 有需要发货的朋友,请直接联系客服咨询。 📲 唯一客服联系方式: @LKtiantian 🤖 24小时快递助手 @YX168bot

2 Aug 2026, 16:38 UTC244 viewsread 15 August 2026
Photo

🇹🇭 泰国 → 斯里兰卡 代购通知 📢 预计一周左右有泰国飞往斯里兰卡航班。 有需要泰国代购、加急采购、顺便带货的客户,请提前报名预约。 🛍️ 代购范围: ✅ 奢侈品(LV、Gucci、Hermès、Chanel 等) ✅ 手表、珠宝首饰 ✅ 手机、平板、笔记本电脑 ✅ 相机、无人机、游戏机 ✅ 美妆护肤、泰国药品、保健品 ✅ 零食、服饰鞋包 ✅ 其他指定商品均可代购 ⚠️ 航班名额有限,本次按报名先后顺序安排采购及带回。 需要加急带回斯里兰卡的,请尽快私信登记,以免错过本次航班。 📩 私信发送商品名称、图片或购买链接,即可报价,一站式采购带回斯里兰卡。 📩 联系客服:@LKtiantian

2 Aug 2026, 15:46 UTC209 viewsread 15 August 2026
Photo

🇱🇰 斯里兰卡入境保关服务 24小时接受预约|中文沟通|一对一对接 ━━━━━━━━━━━━━━ 近期来斯里兰卡的旅客不断增加,为提升抵达体验,现开放机场入境协助预约服务。 🔹 提前了解入境流程 🔹 入境材料咨询与指导 🔹 机场接机安排 🔹 中文全程沟通协助 🔹 行程衔接服务 🔹 一对一预约服务 无论您是旅游、商务考察、探亲还是其他合法出行需求,均可提前联系咨询,根据实际情况提供对应的流程说明及协助。 ━━━━━━━━━━━━━━ 🕒 全天接受预约(建议至少提前24小时联系) 📩 预约及咨询:请直接私信管理员 为保证服务质量,请尽量提前预约。 ━━━━━━━━━━━━━━ 联系客服: @LKanni

30 Jul 2026, 20:42 UTC434 viewsread 15 August 2026
Photo

🔥 麻辣王子辣条清仓处理 📦 一箱起售|仅剩7箱现货 📦 规格:每箱8大包,每包8小袋,一箱共计64小袋 ✅ 全新现货 ✅ 一箱即可发货 ✅ 数量有限,售完即止 💰 价格已放到最底,不议价。 📩 需要的直接私聊,货到付款。 📩 联系客服:@LKtiantian

28 Jul 2026, 17:15 UTC≈1,410 viewsread 15 August 2026
Photo

📢【8月快递航班计划通知】✈️ 为方便大家合理安排发货时间,现公布 8月份快递航班计划: ✈️ 航班日期: • 8月2日 • 8月5日 • 8月8日 • 8月10日 • 8月13日 • 8月17日 • 8月20日 • 8月24日 • 8月27日 • 8月30日 📦 请大家尽量提前安排寄件,避免因临近航班导致仓库集中收货,影响出货效率。 ⚠️ 温馨提示: • 每个航班仓位有限,满仓将顺延至下一班航班。 • 请务必按要求填写收件信息及昵称,方便仓库及时入库、分拣和发货。 • 如遇航空公司调整、天气或海关查验等不可抗力因素,航班时间可能会相应调整,请以最新通知为准。 💬 如需查询包裹、咨询发货或预约仓位,请及时联系客服。 感谢大家一直以来的支持与信任! ━━━━━━━━━━━━ 📩 客服:@LKtiantian 📢 官方频道:@LK123 📋 24小时快递助手 @YX168bot

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

Citation-graph rank

Citation-graph rank — 341,194 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 3 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.

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

“斯里兰卡 空运快递 @LK123” (@LKwuliu), 7,916 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/LKwuliu.

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.