https://m.blog.naver.com/keumssoa/224467714124
❤3🔥2

Channel
@kimcharger
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
25,227subscribers
+436 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001861520498 |
|---|---|
| Type | Channel |
| Username | @kimcharger |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/kimcharger |
Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 42% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 22:35 | 25,227 | +1 |
| 5 Nov 2026, 02:59 | 25,226 | -2 |
| 4 Nov 2026, 04:49 | 25,228 | +32 |
| 3 Nov 2026, 01:09 | 25,196 | +9 |
| 2 Nov 2026, 04:31 | 25,187 | +22 |
| 1 Nov 2026, 05:39 | 25,165 | +24 |
| 31 Oct 2026, 06:19 | 25,141 | +18 |
| 30 Oct 2026, 07:39 | 25,123 | +7 |
| 29 Oct 2026, 10:00 | 25,116 | +14 |
| 28 Oct 2026, 07:14 | 25,102 | +24 |
| 27 Oct 2026, 05:29 | 25,078 | -1 |
| 26 Oct 2026, 02:55 | 25,079 | +5 |
| 25 Oct 2026, 03:16 | 25,074 | +2 |
| 24 Oct 2026, 01:56 | 25,072 | +2 |
| 22 Oct 2026, 22:38 | 25,070 | +1 |
| 21 Oct 2026, 19:09 | 25,069 | +3 |
| 20 Oct 2026, 14:06 | 25,066 | +25 |
| 19 Oct 2026, 15:57 | 25,041 | +10 |
| 18 Oct 2026, 17:04 | 25,031 | +18 |
| 17 Oct 2026, 17:56 | 25,013 | first reading |
349 posts held, back to 12 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 111 pages of Telegram’s post history, 20 posts per page.
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 207 of 213 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 349 (12 August 2026 – 6 November 2026) |
| Views total | 1,106,548 |
| Reactions total | 5,845 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 21:35 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.
9,165 reactions across 340 posts, in 5 distinct kinds. The most used accounts for 51.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4,709 | 51.4% | |
| 👍 | 2,317 | 25.3% | |
| 🔥 | 1,579 | 17.2% | |
| 💯 | 317 | 3.46% | |
| 👌 | 243 | 2.65% |
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 343 of the 349 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 9,165 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 349 most recent posts we hold, published 12 August 2026 to 6 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’s own ‘edited’ marker: 5 of 213 posts held from the last 30 days (2.35%) 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).
https://m.blog.naver.com/keumssoa/224467714124
❤3🔥2
https://m.blog.naver.com/kimcharger/224467337002
👍2❤1
https://youtu.be/4Z5wNpIrOLs?si=_UBUxPDaqkMlqccf
🔥3👍1
앤트로픽 10월 Run Rate 800억 달러 돌파- WSJ 기사 중 26년 2월: 12일 140억 달러 → 월말 190억 달러 초과. 26년 5월: 초순 470억 달러 초과(회사 공식 발표) 26년 7월: 월말 650억 달러 초과(블룸버그·로이터) 26년 9월: 추정치 710억~740억 달러 26년 10월: 월말 800억 달러 초과(WSJ)
❤21
https://n.news.naver.com/mnews/article/366/0001203053?rc=N&ntype=RANKING&sid=001
🔥17
[메리츠증권 반도체/디스플레이 김선우] ▶ 반도체: 삼성전자, SK하이닉스: 미주 채널체크와 역사적 저점 밸류에이션 - 삼성전자, SK하이닉스, 마이크론 등 메모리 업체 미주 영업 마케팅 채널체크 결과, 당장 수요 변화의 이상징후는 감지되지 않는 상황 - 2027년 확정적 (Locked in) 수요 속, 만약 2028년 수요 변동 발생하더라도 다른 고객사들에 의해 전량 흡수될 가능성 높다고 평가 - 민주당 주지사로 변경된 주 역시, 지역 경제 (GDP 및 고용) 감안 시 중장기 DC 사업 제동에는 향후 다양한 변수들이 등장될 것. 아울러 법제화를 통한 변경에도 시간이 필요한 상황 - 이미 메타, 마소 등은 미국 외 DC 건설 검토를 빠르게 착수하고 있음 - 중장기 수요 변화는 충분히 가능. 이는 1) [텍사스, 뉴욕, 조지아, 오레…
❤17👍2
텍사스 주지사 당선인 지나 이노호사, CNN 인터뷰 주요 내용 ■ 데이터센터 신규 인허가 중단 및 규제 강화 “주민 보호 장치가 마련될 때까지 현재 데이터센터와 관련해 추진하고 있는 일을 중단해야 합니다.” 원문: “We need to stop what we are doing with data centers until we have those protections.” → 이번 인터뷰에서는 구체적인 중단 대상을 특정하지 않았으나, 지난 10월 22일에는 주민 보호 법률 제정 전까지 모든 데이터센터 승인을 중단하겠다고 명시. 또한 11월 1일 공개된 KTAB 인터뷰에서는 신규 인허가 중단 조치가 이미 건설 중인 프로젝트에는 적용되지 않는다고 설명 “텍사스는 언제나 기업 친화적인 주였습니다. 하지만 제가 주지사가 되면 기업과 텍사스 주민 …
❤12
탈라리코에 이어 주지사로 당선된 히노호사도 모든 AI DC의 텍사스 설치를 허용할 예정이라고 했고 일론 머스크는 흥미롭다는 반응을 보였네요. 새로 당선된 민주당 정치인들의 공통점은 지역의 일자리를 만드는데 진심이고 동시에 AI DC 건설하려는 기업들에게는 전력,용수 등은 자체 해결하라는 법안을 만들 예정이라 했다네요. ===== 텍사스 주지사 당선인 지나 히노호사(Gina Hinojosa)는 텍사스에서 현재 허가된 모든 데이터센터가 건설을 완료할 수 있도록 허용할 것이라고 명확히 밝혔습니다. 이는 본질적으로 2027년 전체와 아마도 2028년 깊숙이까지를 포괄합니다. 그녀는 앞으로 2028/2029년 인도 예정인 모든 *신규* 허가 데이터센터에 대해 세금을 납부하고, 소비자 전력 가격 인상을 하지 않으며, 사람들의 물 이용 가능성에 …
🔥12❤5
Photo, posted without a caption
❤23
OpenAI) 책임 있는 AI 인프라의 새로운 기준 수립 OpenAI는 미국 내 AI 데이터센터 확충을 지속하면서, 지역사회의 전기요금·환경 부담을 최소화하고 주민과 경제적 이익을 공유하기 위한 새로운 원칙과 정책 제안을 발표. 1. 데이터센터 전력 및 인프라 비용 전액 부담 - OpenAI가 직접 소유·운영하는 향후 모든 데이터센터에서 사용하는 전력과 관련 인프라 비용을 전액 부담. - 프로젝트 지연·축소·취소 시 다른 전력 소비자에게 비용이 전가되지 않도록 착공 전 주요 투자에 대한 재무적 보증 제공. - 주정부 전력규제기관에도 대규모 전력 소비자가 추가적인 전력망 확충 비용을 직접 부담하도록 하는 규정 도입 제안. - AI 데이터센터 때문에 일반 가정의 전기요금이 상승하지 않도록 하는 것이 핵심 목표. 2. 전력망 유연성…
❤10👍2💯1
속보: 레오폴드 아셴브레너 펀드(상황 인식)가 공식적으로 파산한 것으로 알려졌습니다… 현재 보유 자산(청산 완료)은 다음과 같습니다. $MU 1,153달러에 구입했는데 현재 703달러로 (-39%) 하락했습니다. $CORZ 25.6달러에 구입했는데 현재 11.1달러로 (-56%) 하락했습니다. $SNDK 2,268달러에 구입했는데 현재 874달러로 (-61%) 하락했습니다. $NBIS 273달러에 구입했는데, 지금은 121달러로 (-55%) 하락했습니다. $CRWV 99달러에 구입했는데 지금은 42달러 (-57%) - $BE 301달러에 샀는데 지금은 165달러로 떨어졌네요(-45%). 고위험 포지션에 과도한 레버리지를 절대 사용해서는 안 된다는 교훈을 얻으세요. 이것으로 한 시대가 막을 내렸습니다… https://x.com/MrMikeIn…
❤22
https://www.hankyung.com/article/2026110591621
🔥17👍8❤2💯2👌1
Showing the 12 most recent of 349 posts we hold for @kimcharger. 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.
We recorded 2 posts on @kimcharger 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 15 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 47 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“김찰저의 관심과 생각 저장소” (@kimcharger), 25,227 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/kimcharger.
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.