Telegram RegisterThe public register of Telegram
Telegram profile photo for Simon Labs

Channel

Simon Labs

@simonlabs

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

6,003subscribers

+163 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-1003737946150
TypeChannel
Username@simonlabs
Created23 May 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/simonlabs

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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

5,8216,0035,9127 August 2026 — 5,840 subscribers8 August 2026 — 5,836 subscribers11 August 2026 — 5,843 subscribers15 August 2026 — 5,831 subscribers18 August 2026 — 5,821 subscribers20 August 2026 — 5,829 subscribers24 August 2026 — 5,836 subscribers27 August 2026 — 5,853 subscribers2 September 2026 — 5,871 subscribers7 September 2026 — 5,891 subscribers11 September 2026 — 5,926 subscribers14 September 2026 — 5,945 subscribers18 September 2026 — 5,946 subscribers28 September 2026 — 5,960 subscribers5 October 2026 — 5,979 subscribers12 October 2026 — 6,003 subscribers7 August 202612 October 2026
16 measurements spanning 66 days, net +163. 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 5,794–6,030 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 18:076,003+24
5 Oct 2026, 20:415,979+19
28 Sept 2026, 09:175,960+14
18 Sept 2026, 19:565,946+1
14 Sept 2026, 18:165,945+19
11 Sept 2026, 10:375,926+35
7 Sept 2026, 00:405,891+20
2 Sept 2026, 15:045,871+18
27 Aug 2026, 08:355,853+17
24 Aug 2026, 03:285,836+7
20 Aug 2026, 18:585,829+8
18 Aug 2026, 03:545,821-10
15 Aug 2026, 02:145,831-12
11 Aug 2026, 11:275,843+7
8 Aug 2026, 06:185,836-4
7 Aug 2026, 19:325,840first reading

Engagement

7 posts held, back to 23 May 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 7 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 7 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

206 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 77.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍15977.2%
❤4722.8%

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

Measured over the 7 most recent posts we hold, published 23 May 2026 to 30 July 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

30 Jul 2026, 03:48 UTCviews —

Simon Labs pinned «⚠️ 风险提示 近期 Giffgaff 官方对部分长期海外漫游用户进行了限制处理。当前方法可以申请并开通 eSIM,但不代表号码可长期稳定使用,无法对后续号码可用性进行保障。运营商政策及风控规则可能随时调整,请根据自身情况评估风险。»

30 Jul 2026, 03:48 UTC≈3,470 views38 reactionsread 12 August 2026

⚠️ 风险提示 近期 Giffgaff 官方对部分长期海外漫游用户进行了限制处理。当前方法可以申请并开通 eSIM,但不代表号码可长期稳定使用,无法对后续号码可用性进行保障。运营商政策及风控规则可能随时调整,请根据自身情况评估风险。

👍31❤7

16 Jul 2026, 09:52 UTC≈6,920 views59 reactionsread 12 August 2026
File

基于官方 20.27.0 版本修改 🛠 sha1sum: afdfbeea970c2ec14c99fd6e1418e2feffa0fde4 本次更新:🚀 1. 升级到最新 20.27.0 2. 支持LPA Deep Link 直接唤醒 EasyEUICC 或 NekokoLPA 2 3. 新增Apk验证服务 操作手册和常见问题:https://simonmy.com/posts/giffgaff-esim-mod-apk.html 📖 闲聊&讨论群:https://t.me/simonlabs2 💬 如果你基于本方法操作成功,请在博客留言板留言,给后面使用者做指引。👇 有 FAQ 列表以外的问题,我也会优先回复博客留言的信息。📝 🪜推荐:https://xn--4gqx1hgtfdmt.com/#/register?code=7MpyuEnb

👍35❤24

10 Jun 2026, 05:10 UTCviews —

Simon Labs pinned «Giffgaff Mod APK 的目的是帮助迫切需要eSIM,但是暂时没有受支持设备的用户,不是为了大规模传播和赚取流量。 - 如果你已经通过 APK 成功解决了问题,欢迎到文章下面留个言。很多用户遇到的问题其实都差不多,你的反馈可能会帮到后来的人。遇到问题的朋友,也建议先看看评论区,说不定已经有人遇到过并给出了解决方案。如果是新的情况,也欢迎直接留言。原文:https://simonmy.com/posts/giffgaff-esim-mod-apk.html - 转发、转载时,请尽量带上原文地址。…»

10 Jun 2026, 04:54 UTC≈11,400 views109 reactionsread 12 August 2026

Giffgaff Mod APK 的目的是帮助迫切需要eSIM,但是暂时没有受支持设备的用户,不是为了大规模传播和赚取流量。 - 如果你已经通过 APK 成功解决了问题,欢迎到文章下面留个言。很多用户遇到的问题其实都差不多,你的反馈可能会帮到后来的人。遇到问题的朋友,也建议先看看评论区,说不定已经有人遇到过并给出了解决方案。如果是新的情况,也欢迎直接留言。原文:https://simonmy.com/posts/giffgaff-esim-mod-apk.html - 转发、转载时,请尽量带上原文地址。后续如果有更新、补充说明或者方法失效,都会优先更新在原文里。 - 另外,请不要把 APK 单独上传到网盘后到处发给“小白用户”。这看起来是在帮助别人,但从过去的经验来看,短时间内大量无门槛扩散,往往会导致Giffgaff额外关注和风控,最终让现有方法失效。类似情况历史上已经发生过两次。 如果希望这个方法能持续可用,最好的方式不…

👍93❤16

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

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

“Simon Labs” (@simonlabs), 6,003 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/simonlabs.

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.