Telegram RegisterThe public register of Telegram
Telegram profile photo for 三角洲oc内核主频道

Channel

三角洲oc内核主频道

@oc666nb

On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

7,263subscribers

-2,822 since we began measuring on 18 September 2026

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

Register entry

Telegram ID-1004395921433
TypeChannel
Username@oc666nb
Description本频道仅供学习 如有侵权等违法行为请联系删除
Created15 September 2026 — measured — dated from the channel’s first post
First recorded18 September 2026
Last confirmed live8 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/oc666nb

Topic

Hacking & security — 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 5 October 2026 and assigned it the closest of 31 fixed categories, at 70% 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.

Previous handles

@oc666nb was previously reachable at these 2 handles, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@Nova2025
held 30 September 2026 – 30 September 2026
@SV6600
held 18 September 2026 – 18 September 2026

Growth

7,26311,2539,25818 September 2026 — 10,085 subscribers25 September 2026 — 11,004 subscribers30 September 2026 — 11,182 subscribers5 October 2026 — 11,195 subscribers9 October 2026 — 11,214 subscribers13 October 2026 — 11,237 subscribers14 October 2026 — 11,249 subscribers15 October 2026 — 11,253 subscribers16 October 2026 — 11,246 subscribers17 October 2026 — 11,181 subscribers18 October 2026 — 11,110 subscribers19 October 2026 — 11,043 subscribers20 October 2026 — 10,867 subscribers21 October 2026 — 10,746 subscribers22 October 2026 — 10,613 subscribers23 October 2026 — 10,498 subscribers25 October 2026 — 10,370 subscribers25 October 2026 — 10,317 subscribers26 October 2026 — 10,215 subscribers27 October 2026 — 10,121 subscribers28 October 2026 — 10,026 subscribers29 October 2026 — 9,910 subscribers2 November 2026 — 9,618 subscribers2 November 2026 — 9,618 subscribers2 November 2026 — 9,619 subscribers5 November 2026 — 9,264 subscribers8 November 2026 — 7,263 subscribers18 September 20268 November 2026
27 measurements spanning 51 days, net -2,822. 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 6,665–11,852 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
8 Nov 2026, 14:167,263-2,001
5 Nov 2026, 02:549,264-355
2 Nov 2026, 08:319,619+1
2 Nov 2026, 04:559,618no change
2 Nov 2026, 04:479,618-292
29 Oct 2026, 18:519,910-116
28 Oct 2026, 21:3610,026-95
27 Oct 2026, 22:0610,121-94
26 Oct 2026, 18:5810,215-102
25 Oct 2026, 20:4710,317-53
25 Oct 2026, 00:0410,370-128
23 Oct 2026, 22:1610,498-115
22 Oct 2026, 20:4610,613-133
21 Oct 2026, 15:4110,746-121
20 Oct 2026, 14:4010,867-176
19 Oct 2026, 15:4411,043-67
18 Oct 2026, 14:4011,110-71
17 Oct 2026, 14:3911,181-65
16 Oct 2026, 17:0511,246-7
15 Oct 2026, 19:4711,253first reading

Engagement

4 posts held, back to 15 September 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 18 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.77%
avg views ÷ 7,263 subscribers
Avg views / post
129
2 posts measured
Reaction rate
3.11%
reactions ÷ views · ER floor
Posts in window
2
of 4 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 9 November 2026
Posts held4 (15 September 2026 – 9 November 2026)
Views total257
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 02:29 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
3
Links
1

Lifetime counters from Telegram’s own channel header, read 10 November 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.

Reaction mix

624 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 36.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤23036.9%
🔥19831.7%
👍19631.4%

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

Measured over the 4 most recent posts we hold, published 15 September 2026 to 9 November 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

Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Sept 2026, 17:54 UTC≈78,200 views616 reactionsread 10 November 2026
Photo

⭐三角洲知音尊享版⭐ 🥰尊享版: 支持骁龙、天玑5-6系所有内核版本,千人千面算法解密无延迟无拖框无集体,触摸自瞄软锁不动任何内存,概率追踪稳定奔放,掩体变色漏打物资透 功能齐全 ✅【官方频道】:点我加入 ✅【提卡地址】:点我购买 ✅【客服售后】:@zy666kf ————————————— ✔️售后服务请携带订单截图·找客服给与售后服务。 ✔️产品均为自愿购买,请仔细考虑并确认是否购买。

❤230🔥198👍188

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

Posts edited after publishing

@oc666nb edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
3 November 2026
Most recent edit
9 November 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @oc666nb as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
3 November 2026
Most recent seen missing
9 November 2026
Median time before seen missing
40 days
Seen missing in the last 30 days
3

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 2 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.

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

“三角洲oc内核主频道” (@oc666nb), 7,263 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/oc666nb.

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.