Telegram RegisterThe public register of Telegram
Telegram profile photo for OE通知频道

Channel

OE通知频道

@BoBoNotify

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry

35,215subscribers

-2,270 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001863963525
TypeChannel
Username@BoBoNotify
DescriptionOE只有一个频道一个群组,其他均为冒充。 作者 @OE9996 频道: @BoBoNotify 唯一群组:https://t.me/BoBoCheat 赞赏下载:http://www.oekernel.com/ 问题解决 https://t.me/OEBUG1
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live29 October 2026
Measurements held52
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/BoBoNotify

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

Growth

35,21537,49636,355.57 August 2026 — 37,485 subscribers7 August 2026 — 37,485 subscribers8 August 2026 — 37,496 subscribers9 August 2026 — 37,448 subscribers10 August 2026 — 37,445 subscribers11 August 2026 — 37,470 subscribers12 August 2026 — 37,468 subscribers14 August 2026 — 37,442 subscribers15 August 2026 — 37,370 subscribers16 August 2026 — 37,290 subscribers17 August 2026 — 37,256 subscribers18 August 2026 — 37,220 subscribers19 August 2026 — 37,199 subscribers20 August 2026 — 37,204 subscribers22 August 2026 — 37,160 subscribers23 August 2026 — 37,091 subscribers25 August 2026 — 37,068 subscribers26 August 2026 — 37,001 subscribers27 August 2026 — 36,992 subscribers28 August 2026 — 36,972 subscribers29 August 2026 — 36,930 subscribers30 August 2026 — 36,910 subscribers31 August 2026 — 36,916 subscribers1 September 2026 — 36,973 subscribers2 September 2026 — 36,953 subscribers3 September 2026 — 36,915 subscribers5 September 2026 — 36,857 subscribers8 September 2026 — 36,787 subscribers11 September 2026 — 36,714 subscribers13 September 2026 — 36,639 subscribers14 September 2026 — 36,634 subscribers16 September 2026 — 36,603 subscribers19 September 2026 — 36,528 subscribers26 September 2026 — 36,340 subscribers4 October 2026 — 36,035 subscribers8 October 2026 — 35,880 subscribers13 October 2026 — 35,747 subscribers14 October 2026 — 35,681 subscribers15 October 2026 — 35,651 subscribers16 October 2026 — 35,605 subscribers17 October 2026 — 35,585 subscribers18 October 2026 — 35,551 subscribers19 October 2026 — 35,510 subscribers20 October 2026 — 35,473 subscribers21 October 2026 — 35,437 subscribers22 October 2026 — 35,395 subscribers23 October 2026 — 35,364 subscribers24 October 2026 — 35,327 subscribers25 October 2026 — 35,308 subscribers26 October 2026 — 35,278 subscribers27 October 2026 — 35,245 subscribers29 October 2026 — 35,215 subscribers7 August 202629 October 2026
52 measurements spanning 82 days, net -2,270. 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 34,873–37,838 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 52
Measured (UTC)SubscribersChange
29 Oct 2026, 02:1935,215-30
27 Oct 2026, 23:4635,245-33
26 Oct 2026, 21:0235,278-30
25 Oct 2026, 23:0935,308-19
24 Oct 2026, 20:5135,327-37
23 Oct 2026, 18:0835,364-31
22 Oct 2026, 18:5135,395-42
21 Oct 2026, 16:0535,437-36
20 Oct 2026, 14:3835,473-37
19 Oct 2026, 16:4735,510-41
18 Oct 2026, 15:3635,551-34
17 Oct 2026, 12:1035,585-20
16 Oct 2026, 11:4635,605-46
15 Oct 2026, 12:2135,651-30
14 Oct 2026, 14:3135,681-66
13 Oct 2026, 03:0635,747-133
8 Oct 2026, 22:0235,880-155
4 Oct 2026, 11:4136,035-305
26 Sept 2026, 01:1636,340-188
19 Sept 2026, 07:5536,528first reading

Engagement

264 posts held, back to 3 August 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 158 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.29%
avg views ÷ 35,215 subscribers
Avg views / post
1,510
33 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
42
of 264 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 October 2026
Posts held264 (3 August 2026 – 26 October 2026)
Views total49,906
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Oct 2026, 04:52 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.

What this channel posts

Photos
16
Videos
1
Links
2

Lifetime counters from Telegram’s own channel header, read 29 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
4m 18s
Average length
32s

Measured directly from 8 videos 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.

Recent posts

26 Oct 2026, 11:15 UTCviews —

OE通知频道 pinned «免责申明 1. 本软件所有代码来源于ChatGPT,仅为技术验证及海外用户共同训练使用,严禁用于任何商业用途(包括但不限于付费推广、盈利性服务、二次开发后售卖等),违规使用产生的法律责任及经济损失由使用者自行承担。 2. 本模型仅限海外用户参与共同训练,参与训练前需确保自身符合所在地区的法律法规,禁止任何境内用户以任何形式(包括但不限于跨境代理、他人代注册等)参与训练或使用,违规参与导致的一切后果由使用者负责。 3. 模型训练及使用仅为“可控制、防泛滥”的技术验证目的,使用者不得对模型进行反向工程、…»

26 Oct 2026, 11:15 UTC874 viewsread 29 October 2026

免责申明 1. 本软件所有代码来源于ChatGPT,仅为技术验证及海外用户共同训练使用,严禁用于任何商业用途(包括但不限于付费推广、盈利性服务、二次开发后售卖等),违规使用产生的法律责任及经济损失由使用者自行承担。 2. 本模型仅限海外用户参与共同训练,参与训练前需确保自身符合所在地区的法律法规,禁止任何境内用户以任何形式(包括但不限于跨境代理、他人代注册等)参与训练或使用,违规参与导致的一切后果由使用者负责。 3. 模型训练及使用仅为“可控制、防泛滥”的技术验证目的,使用者不得对模型进行反向工程、拆解、篡改代码或衍生新模型,一经发现,需承担由此造成的技术风险及法律责任。 4. 请勿将本软件及模型传播至国内任何平台(包括但不限于社交软件、视频平台、论坛、网盘等),也不得通过私下分享、链接转发等方式扩散给境内人员,传播行为产生的合规风险及连带责任由传播者自行承担。 5. 要求使用者下载本模型后24小时内完成训练参与并彻底…

25 Oct 2026, 16:02 UTC228 viewsread 29 October 2026

免责申明 1. 本软件所有代码来源于ChatGPT,仅为技术验证及海外用户共同训练使用,严禁用于任何商业用途(包括但不限于付费推广、盈利性服务、二次开发后售卖等),违规使用产生的法律责任及经济损失由使用者自行承担。 2. 本模型仅限海外用户参与共同训练,参与训练前需确保自身符合所在地区的法律法规,禁止任何境内用户以任何形式(包括但不限于跨境代理、他人代注册等)参与训练或使用,违规参与导致的一切后果由使用者负责。 3. 模型训练及使用仅为“可控制、防泛滥”的技术验证目的,使用者不得对模型进行反向工程、拆解、篡改代码或衍生新模型,一经发现,需承担由此造成的技术风险及法律责任。 4. 请勿将本软件及模型传播至国内任何平台(包括但不限于社交软件、视频平台、论坛、网盘等),也不得通过私下分享、链接转发等方式扩散给境内人员,传播行为产生的合规风险及连带责任由传播者自行承担。 5. 要求使用者下载本模型后24小时内完成训练参与并彻底…

24 Oct 2026, 22:24 UTC315 viewsread 29 October 2026

免责申明 1. 本软件所有代码来源于ChatGPT,仅为技术验证及海外用户共同训练使用,严禁用于任何商业用途(包括但不限于付费推广、盈利性服务、二次开发后售卖等),违规使用产生的法律责任及经济损失由使用者自行承担。 2. 本模型仅限海外用户参与共同训练,参与训练前需确保自身符合所在地区的法律法规,禁止任何境内用户以任何形式(包括但不限于跨境代理、他人代注册等)参与训练或使用,违规参与导致的一切后果由使用者负责。 3. 模型训练及使用仅为“可控制、防泛滥”的技术验证目的,使用者不得对模型进行反向工程、拆解、篡改代码或衍生新模型,一经发现,需承担由此造成的技术风险及法律责任。 4. 请勿将本软件及模型传播至国内任何平台(包括但不限于社交软件、视频平台、论坛、网盘等),也不得通过私下分享、链接转发等方式扩散给境内人员,传播行为产生的合规风险及连带责任由传播者自行承担。 5. 要求使用者下载本模型后24小时内完成训练参与并彻底…

23 Oct 2026, 17:25 UTC≈1,710 viewsread 29 October 2026

KPM -QX 别勾选模型漏打 因为不支持多线程读取数据 之前的模型读取方案(syscall)不稳定 所以取消了 现在模型读取全部依靠驱动

23 Oct 2026, 17:14 UTCviews —

OE通知频道 pinned «修复加固导致勾选内核追索初始化失败问题 已推送»

23 Oct 2026, 17:14 UTC≈1,670 viewsread 29 October 2026

修复加固导致勾选内核追索初始化失败问题 已推送

23 Oct 2026, 13:02 UTC≈1,720 viewsread 29 October 2026

新的模型漏打 如果驱动不支持多线程快读 会造成卡顿 换驱动 或者不勾选漏打

23 Oct 2026, 02:05 UTC≈1,870 viewsread 29 October 2026
Video

即将更新 重要更新 稳定驱动完全重构 读取数据提速 更安全的断点 1.新的的断点追 2.断点瞄 3.断点无后 4.断点广角 5.狂暴 战斗 追 锁 悬浮按钮改变样式 6.修复5系不刷过CFI模块会重启问题 7.彻底修复因为部分数据获取不到导致自瞄看天问题 8.彻底修复骨骼乱画问题 9.修复解密失效问题 10.漏打模型加载改为更安全的读取 CFM将上线 绘制 + 断点追

19 Oct 2026, 22:04 UTC733 viewsread 29 October 2026

免责申明 1. 本软件所有代码来源于ChatGPT,仅为技术验证及海外用户共同训练使用,严禁用于任何商业用途(包括但不限于付费推广、盈利性服务、二次开发后售卖等),违规使用产生的法律责任及经济损失由使用者自行承担。 2. 本模型仅限海外用户参与共同训练,参与训练前需确保自身符合所在地区的法律法规,禁止任何境内用户以任何形式(包括但不限于跨境代理、他人代注册等)参与训练或使用,违规参与导致的一切后果由使用者负责。 3. 模型训练及使用仅为“可控制、防泛滥”的技术验证目的,使用者不得对模型进行反向工程、拆解、篡改代码或衍生新模型,一经发现,需承担由此造成的技术风险及法律责任。 4. 请勿将本软件及模型传播至国内任何平台(包括但不限于社交软件、视频平台、论坛、网盘等),也不得通过私下分享、链接转发等方式扩散给境内人员,传播行为产生的合规风险及连带责任由传播者自行承担。 5. 要求使用者下载本模型后24小时内完成训练参与并彻底…

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

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

“OE通知频道” (@BoBoNotify), 35,215 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/BoBoNotify.

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.