Telegram RegisterThe public register of Telegram

Channel

매경 월가월부

@mkglobalinvest

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

16,196subscribers

+5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001288659153
TypeChannel
Username@mkglobalinvest
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/mkglobalinvest

Topic

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 91% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@awake_globalwatch/223307 Aug 2026, 14:22 UTC@mkglobalinvest/6731 · this entry7 Aug 2026, 14:22 UTC1.00under a minute
@awake_globalwatch/223317 Aug 2026, 14:23 UTC@mkglobalinvest/6732 · this entry7 Aug 2026, 14:23 UTC1.00under a minute
@awake_globalwatch/223327 Aug 2026, 14:24 UTC@mkglobalinvest/6733 · this entry7 Aug 2026, 14:24 UTC1.00under a minute
@awake_globalwatch/223337 Aug 2026, 14:25 UTC@mkglobalinvest/6734 · this entry7 Aug 2026, 14:25 UTC1.00under a minute
@awake_globalwatch/223347 Aug 2026, 14:30 UTC@mkglobalinvest/6735 · this entry7 Aug 2026, 14:30 UTC1.00under a minute
@awake_globalwatch/223357 Aug 2026, 14:32 UTC@mkglobalinvest/6736 · this entry7 Aug 2026, 14:32 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@awake_globalwatch8 (8/8 hand-verifiable sample passed)1.00under a minute@awake_globalwatch (80)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 8 of the 8 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 5 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @awake_globalwatch. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

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.

Growth

16,19116,20616,198.57 August 2026 — 16,191 subscribers7 August 2026 — 16,191 subscribers7 August 2026 — 16,196 subscribers8 August 2026 — 16,201 subscribers9 August 2026 — 16,203 subscribers10 August 2026 — 16,206 subscribers11 August 2026 — 16,204 subscribers12 August 2026 — 16,196 subscribers16,1967 August 202612 August 2026
8 measurements spanning 5 days, net +5. 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 16,189–16,208 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 15:4316,196-8
11 Aug 2026, 16:2216,204-2
10 Aug 2026, 16:5316,206+3
9 Aug 2026, 16:0216,203+2
8 Aug 2026, 18:4316,201+5
7 Aug 2026, 19:5016,196+5
7 Aug 2026, 14:3016,191no change
7 Aug 2026, 14:2716,191first reading

Engagement

47 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
10.2%
avg views ÷ 16,196 subscribers
Avg views / post
1,640
47 posts measured
Reaction rate
0.096%
reactions ÷ views · ER floor
Posts in window
47
of 47 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 24 of 47 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held47 (5 August 202612 August 2026)
Views total77,296
Reactions total38
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 10:13 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

38 reactions across 23 posts, in 2 distinct kinds. The most used accounts for 71.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2771.1%
👍1128.9%

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

Measured over the 47 most recent posts we hold, published 5 August 2026 to 12 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

12 Aug 2026, 03:19 UTC≈1,000 viewsread 12 August 2026

[어바웃 뉴욕] 샐러드 공포가 덮친 미국…카바는 왜 스위트그린과 달랐나 | 이나연 특파원 https://www.youtube.com/watch?v=YZc2620fAj8

11 Aug 2026, 21:29 UTC≈1,330 views1 reactionsread 12 August 2026

[문지웅의 빅머니 LIVE] 엔비디아 5천억불 AI 파이낸싱 | 웰스파고 "여전히 의문 | "BofA "순환금융에서 벗어났다" | 코어위브 시간외 14% 폭등 https://www.youtube.com/watch?v=M1ESaXWUOa0

1

11 Aug 2026, 14:47 UTC≈1,340 viewsread 12 August 2026
Photo

🇺🇸 Everpure(+4.9%) ❗️ 역사적 신고가 신규 돌파 Sector : Industrials Industry : Industrial - Machinery 종목코드 : P 시가총액 : 34.2B(51.0조 krw) 거래대금 : 130mil(1917억 krw) 시총순위 : 369 → 360위(9계단🔺) [기업개요] - 정수기 및 수처리 솔루션을 제공하는 업체 - 북미와 유럽 시장에서 주력 제품인 상업용 정수기와 필터를 통해 매출 발생 - 주요 성장동력은 친환경 수처리 기술 개발과 글로벌 시장 확장

11 Aug 2026, 14:45 UTC≈1,130 viewsread 12 August 2026
Photo

🇺🇸 Twilio(+2.6%) ❗️ 52주 신고가 돌파 이어감 Sector : Technology Industry : Software - Infrastructure 종목코드 : TWLO 시가총액 : 38.9B(58.0조 krw) 거래대금 : 134mil(1976억 krw) 시총순위 : 339 → 332위(7계단🔺) [기업개요] - 클라우드 기반 통신 플랫폼 제공업체 - 메시징, 음성, 비디오 API를 통한 다양한 기업 고객 지원 - 주요 성장동력은 고객 맞춤형 솔루션과 글로벌 확장 전략

11 Aug 2026, 14:38 UTC955 viewsread 12 August 2026
Photo

🇺🇸 Marathon Petroleum(+2.9%) ❗️ 역사적 신고가 돌파 Sector : Energy Industry : Oil & Gas Refining & Marketing 종목코드 : MPC 시가총액 : 96.2B(142.0조 krw) 거래대금 : 157mil(2320억 krw) 시총순위 : 145 → 143위(2계단🔺) [기업개요] - 정유 및 석유화학 제품을 생산하는 에너지 업체 - 원유 정제 및 유통을 통해 안정적인 매출 기반 확보 - 주요 성장동력은 정제 마진 개선 및 석유화학 사업 확장

11 Aug 2026, 14:36 UTC861 viewsread 12 August 2026
Photo

🇺🇸 Bank of Montreal(+0.3%) ❗️ 역사적 신고가 돌파 이어감 Sector : Financial Services Industry : Banks - Diversified 종목코드 : BMO 시가총액 : 127.7B(189.0조 krw) 거래대금 : 11mil(167억 krw) [기업개요] - 캐나다 기반의 금융 서비스 제공업체 - 주력 사업은 개인 및 상업 금융, 자산 관리, 투자 은행 - 북미 시장에서의 강력한 입지와 디지털 금융 서비스 확장이 주요 성장동력

11 Aug 2026, 14:35 UTC855 viewsread 12 August 2026
Photo

🇺🇸 Eaton(+3.8%) ❗️ 역사적 신고가 돌파 이어감 Sector : Industrials Industry : Electrical Equipment & Parts 종목코드 : ETN 시가총액 : 179.4B(266.0조 krw) 거래대금 : 157mil(2321억 krw) 시총순위 : 79 → 74위(5계단🔺) [기업개요] - 전력 관리 및 산업 자동화 솔루션을 제공하는 글로벌 업체 - 전기차 충전 인프라 및 에너지 저장 시스템 분야에서의 확장 - 주요 성장동력은 지속 가능한 에너지 솔루션 및 전력 관리 기술

11 Aug 2026, 14:33 UTC772 viewsread 12 August 2026
Photo

🇺🇸 Amgen(-0.7%) ❗️ 역사적 신고가 돌파 이어감 Sector : Healthcare Industry : Drug Manufacturers - General 종목코드 : AMGN 시가총액 : 223.6B(331.0조 krw) 거래대금 : 86mil(1270억 krw) [기업개요] - 생명공학 분야에서 혁신적인 바이오의약품 개발 및 상업화에 주력하는 업체 - 면역학, 종양학, 심혈관계 질환 등 다양한 치료 영역에서 강력한 제품 포트폴리오 보유 - 주요 성장동력은 신약 개발과 글로벌 시장 확장 전략

11 Aug 2026, 14:32 UTC865 viewsread 12 August 2026
Photo

🇺🇸 Bank of America(0%) ❗️ 역사적 신고가 돌파 이어감 Sector : Financial Services Industry : Banks - Diversified 종목코드 : BAC 시가총액 : 453.4B(671.0조 krw) 거래대금 : 279mil(4133억 krw) [기업개요] - 금융 서비스 제공업체로, 주력 사업은 소비자 금융, 기업 금융, 자산 관리 - 최근 디지털 뱅킹 플랫폼 강화 및 고객 경험 개선에 집중 - 주요 매출원은 대출 및 예금 서비스, 투자 은행 부문 성장동력

11 Aug 2026, 14:31 UTC≈1,020 viewsread 12 August 2026
Photo

🇺🇸 Eli Lilly and Company(-1.5%) ❗️ 역사적 신고가 신규 돌파 Sector : Healthcare Industry : Drug Manufacturers - General 종목코드 : LLY 시가총액 : 1142.5B(1691.0조 krw) 거래대금 : 485mil(7176억 krw) [기업개요] - 글로벌 제약 및 생명공학 업체로 신약 개발과 혁신적 치료제 제공에 주력 - 당뇨병, 암, 면역질환 등 다양한 분야에서 강력한 제품 포트폴리오 보유 - 주요 매출원은 당뇨병 치료제와 면역질환 치료제에서 발생

11 Aug 2026, 13:24 UTC≈1,350 views1 reactionsread 12 August 2026

모건스탠리 “메모리 조달 FOMO”ㅣ앤트로픽·유니트리 상장 러시ㅣ브렌트유 장중 90달러 돌파ㅣ테슬라·스페이스X 합병, 머스크 1조달러 잭팟? | 홍혜진의 뉴욕브리핑 https://www.youtube.com/watch?v=vaVGAtlxGfI

👍1

10 Aug 2026, 21:33 UTC≈1,750 views2 reactionsread 12 August 2026

[문지웅의 빅머니 LIVE] 모건스탠리 이번엔 메모리 강세론 | 스페이스X 공모가 돌파 | 엔화 다시 약세 FIMA레포 사용임박 https://www.youtube.com/watch?v=FUbzq2Z4ucw

1👍1

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

Citation-graph rank

Citation-graph rank — 934,774 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“매경 월가월부” (@mkglobalinvest), 16,196 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/mkglobalinvest.

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.