Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 50% 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
61 measurements spanning 91 days, net -6,580. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)
Subscribers
Change
4 Nov 2026, 15:16
73,068
-6
4 Nov 2026, 13:22
73,074
+73,073
4 Nov 2026, 11:19
1
-73,193
3 Nov 2026, 03:38
73,194
-49
2 Nov 2026, 04:40
73,243
-62
1 Nov 2026, 01:19
73,305
-51
31 Oct 2026, 03:07
73,356
-56
30 Oct 2026, 03:48
73,412
-35
29 Oct 2026, 06:27
73,447
-86
28 Oct 2026, 01:36
73,533
-70
27 Oct 2026, 00:40
73,603
-53
25 Oct 2026, 21:50
73,656
-67
24 Oct 2026, 18:58
73,723
-58
23 Oct 2026, 21:17
73,781
-41
22 Oct 2026, 18:51
73,822
-65
21 Oct 2026, 15:20
73,887
-65
20 Oct 2026, 11:56
73,952
-40
19 Oct 2026, 10:34
73,992
-46
18 Oct 2026, 13:36
74,038
-40
17 Oct 2026, 15:28
74,078
first reading
Engagement
92 posts held, back to 29 June 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 181 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
2.73%
avg views ÷ 73,068 subscribers
Avg views / post
2,000
13 posts measured
Reaction rate
0.262%
reactions ÷ views · ER floor
Posts in window
15
of 92 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 12 of 13 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 4 November 2026
Posts held
92 (29 June 2026 – 4 November 2026)
Views total
25,977
Reactions total
66
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
4 Nov 2026, 13:22 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
1,169 reactions across 84 posts, in 7 distinct kinds. The most used accounts for 60.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
703
60.1%
🔥
169
14.5%
⚡
128
10.9%
👍
126
10.8%
💯
23
1.97%
🤩
18
1.54%
👏
2
0.171%
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 84 of the 92 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 1,169 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 92 most recent posts we hold, published 29 June 2026 to 4 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.
Telegram Stars
Stars received
18
across the posts below
Posts paid on
9
of 85 we hold a reading for · 11%
Most on one post
4
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ONE_KR_Official. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 92 most recent posts we hold for this entry, published 29 June 2026 to 4 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 15 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).
This Telegram channel is becoming ONE KR. We’re reorganizing our channels so you can follow the updates that matter to you. ONE KR will focus on ONE services and content for audiences in Korea, with future posts primarily in Korean.
If you prefer English updates, follow ONEstore Global for ONEstore product news and service updates. For ONEchain ecosystem updates, follow ONEchain: https://t.me/one_gamechain
ONEstore …
Switching devices in EOS RED: Rebirth? Link your account first.
Use Google or Apple through the official site to keep playing with the same account and progress.
The account-linking event code STARTREBIRTH1006 closes on November 3, 14:59 UTC. One redemption per account; collect the items from your in-game mailbox within 14 days.
Read the linking guide and coupon conditions
Final day for two EOS RED: Rebirth launch codes.
NEWSTART and GRANDOPEN close on October 31, 14:59 UTC.
Link your account and register eligible codes through the official site. Each code can be used once per account. Then collect the rewards from your in-game mailbox within 14 days.
NEWSTART conditions · GRANDOPEN conditions
🛡️ Your next step: preregister for THE GUARDIANS.
If the game caught your eye, visit the official preregistration page and check the linked ONEquest challenge.
🎁 100 lucky pre-registrants will win 100 stONE each.
This is a prize draw, not a guaranteed reward for every participant. Check the official quest page for participation and reward conditions.
👉 Pre-register for THE GUARDIANS
👉 Open the ONEquest challenge
Frost Kingdom Servers 1 and 2: check the planned merge.
The official pre-announcement gives October 29 KST as the planned date. The schedule may change.
Exact maintenance hours and data-handling rules will be provided in a separate notice. Check that update before planning your session.
Read the server-merge notice
Daily withdrawal limit reached? Use the UTC reset, not local midnight.
ONEquest’s daily limit resets at 00:00 UTC. Your tier determines both the daily limit and withdrawal fee.
Before the next request, check You will Receive for the amount after the fee. KYC is required, and requests are reviewed before payment—resetting the limit does not make the payout instant.
Read the withdrawal conditions
7 Lucky Boxes is not 7 ONE.
THE GUARDIANS' current pre-registration quest lists 7 Lucky Boxes. These are used for draws within ONEquest—not a withdrawable token balance or a guaranteed draw prize.
This is a one-time quest. Open the quest, use its official pre-registration entry and meet the listed account-linking and verification requirements. A page visit alone is not completion.
Check THE GUARDIANS quest and par…
AVA RE:BIRTH on your radar? Make your pre-registration count. 🎯
100 lucky pre-registrants will win 100 ONE each.
Check the ONEquest entry guide and complete the required steps before Oct 28, 00:00 UTC:
https://www.onechain.nexus/quest/quests/15
🛡️ THE GUARDIANS: Pre-register, then complete your ONEquest mission
The preregistration quest for THE GUARDIANS is now live on ONEquest.
How to take part
1. Pre-register on the official THE GUARDIANS page.
2. Check your inbox for the preregistration email.
3. Copy the code from the email.
4. Paste it into the UUID field on the ONEquest quest page and follow the verification steps.
🎁 100 lucky pre-registrants will…
A genre detour works when ONE concrete hook leads the way — combat rhythm, character chemistry, or a world worth getting lost in.
👉 Open ONEquest
👍6❤2
Showing the 12 most recent of 92 posts we hold for @ONE_KR_Official. 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
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 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.
Handles this channel named that no longer answer
Dead references
4
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
4
vacant every time we have ever looked
@ONE_KR_Official named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@onequest_xyz named in 29 posts, 10 September 2026 – 2 October 2026
@krakenfx named in 12 posts, 10 September 2026 – 29 September 2026
@frost_kingdom_ named in 8 posts, 10 September 2026 – 27 September 2026
@onechain_game named in 3 posts, 15 September 2026 – 27 September 2026
Domains linked from posts
6 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 4 November 2026 — this
entry's latest reading, not the date you are reading this.
“ONE KR” (@ONE_KR_Official), 73,068 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/ONE_KR_Official.
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.