Telegram RegisterThe public register of Telegram
Telegram profile photo for 光卡科技

Channel

光卡科技

@HikariCalyxTechCN

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

997subscribers

+74 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002829593131
TypeChannel
Username@HikariCalyxTechCN
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/HikariCalyxTechCN

Topic

Technology — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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

9239979606 August 2026 — 923 subscribers6 August 2026 — 923 subscribers15 August 2026 — 944 subscribers21 August 2026 — 949 subscribers27 August 2026 — 977 subscribers12 September 2026 — 983 subscribers25 September 2026 — 997 subscribers6 August 202625 September 2026
7 measurements spanning 50 days, net +74. 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 912–1,008 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 06:01997+14
12 Sept 2026, 13:18983+6
27 Aug 2026, 13:34977+28
21 Aug 2026, 14:06949+5
15 Aug 2026, 10:26944+21
6 Aug 2026, 14:04923no change
6 Aug 2026, 02:51923first reading

Engagement

16 posts held, back to 15 July 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 16 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

161 reactions across 10 posts, in 11 distinct kinds. The most used accounts for 50.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8150.3%
😁2314.3%
🌚2012.4%
🤣148.70%
🤡95.59%
🥰84.97%
🤩21.24%
❤10.621%
🎉10.621%
👏10.621%
🤗10.621%

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

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

5 Aug 2026, 12:56 UTC234 views6 reactionsread 6 August 2026

https://telegra.ph/%E4%BD%BF%E7%94%A8-iPhone-%E5%9C%A8%E5%9B%BD%E5%86%85%E6%BF%80%E6%B4%BB-CTE-%E7%9A%84%E6%95%99%E7%A8%8B-08-05

👍6

4 Aug 2026, 16:13 UTC330 views13 reactionsread 6 August 2026

需要以我个人经验,写cte拉wifi calling在国内的激活教程吗?

👍9😁3🤗1

4 Aug 2026, 12:52 UTC359 views3 reactionsread 6 August 2026

如果在中国网络发短信,那一条短信就是10便士,比英国土特产略贵。 我打算前期投入相当于一件衬衫的价格来使用cte。

🤣3

4 Aug 2026, 12:48 UTC366 viewsread 6 August 2026

在能够这样激活CTExcel的前提下,后期保号成本大约是一年30便士。 计算方法如下: 1. CTE规定90天内至少产生一次消费或者有有效套餐。 2. 英国本土和欧盟国家内,PAYG范围内发送短信一条6便士。 3. 为了万无一失,你要稍微略短于90天发一次短信,也就是一年五次短信,这样就是30便士。 CTE允许用支付宝或微信支付充话费,不需要像前英国土特产那样买个充值卡或是上VM信用卡。

4 Aug 2026, 11:49 UTC371 viewsread 6 August 2026

如果各位需要的话,这是我用的机场的AFF: https://wd-gold.net/aff.php?aff=12644

4 Aug 2026, 11:09 UTC369 viewsread 6 August 2026
Photo

把软路由改成全局模式、连接位于英国的机场、不绕过大陆之后,CTE激活成功了。

30 Jul 2026, 13:45 UTC793 views2 reactionsread 6 August 2026

现在换了乌龟卡,英国土特产我只绑了apple ID和discord,第一时间换绑了,问题不大。

🌚2

29 Jul 2026, 23:47 UTC824 views20 reactionsread 6 August 2026
Photo

英国土特产封号终于也轮到我了😭

🌚18🎉1👏1

24 Jul 2026, 15:53 UTC≈1,680 views4 reactionsread 6 August 2026
Photo

正在开发用于2017-2019年的FIH机型的刷机工具OSTRemote3,并将全面用它淘汰原本的刷机工具和bootloader解锁工具。 以及,为了照顾某些用户的需求,它也将提供Linux和macOS版本。

🥰4

24 Jul 2026, 15:42 UTC≈1,740 views28 reactionsread 6 August 2026

再声明一点:本频道主不玩手游,不玩腾讯游戏(包括英雄联盟、DNF、三角洲),不玩mihoyo/hoyoverse的游戏。 我这里主要玩的网游有且仅有一款,就是MapleStory。

😁16🤣11❤1

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

Forward network

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.

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.

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

“光卡科技” (@HikariCalyxTechCN), 997 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/HikariCalyxTechCN.

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.