연간 CAPEX 1t를 하려면 매출이 4t가 나와야 함
❤11

Channel
@rafikiresearch
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
20,669subscribers
+327 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001171797194 |
|---|---|
| Type | Channel |
| Username | @rafikiresearch |
| Description | Global macro research |
| Created | 10 February 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/rafikiresearch |
National news — 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 48% 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 |
|---|---|---|
| 15 Nov 2026, 08:50 | 20,669 | +13 |
| 12 Nov 2026, 01:50 | 20,656 | +2 |
| 10 Nov 2026, 00:00 | 20,654 | -7 |
| 8 Nov 2026, 14:59 | 20,661 | -12 |
| 7 Nov 2026, 08:38 | 20,673 | -1 |
| 6 Nov 2026, 09:07 | 20,674 | +16 |
| 5 Nov 2026, 05:26 | 20,658 | +12 |
| 4 Nov 2026, 07:16 | 20,646 | +24 |
| 3 Nov 2026, 08:15 | 20,622 | -6 |
| 2 Nov 2026, 10:05 | 20,628 | +7 |
| 1 Nov 2026, 07:01 | 20,621 | -3 |
| 31 Oct 2026, 04:01 | 20,624 | +2 |
| 30 Oct 2026, 01:06 | 20,622 | +30 |
| 27 Oct 2026, 20:15 | 20,592 | -7 |
| 26 Oct 2026, 23:09 | 20,599 | +50 |
| 26 Oct 2026, 01:40 | 20,549 | -2 |
| 25 Oct 2026, 04:50 | 20,551 | -2 |
| 24 Oct 2026, 07:27 | 20,553 | -1 |
| 23 Oct 2026, 10:27 | 20,554 | +3 |
| 22 Oct 2026, 12:16 | 20,551 | first reading |
838 posts held, back to 5 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 86 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 244 of 275 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 838 (5 August 2026 – 17 November 2026) |
| Views total | 972,004 |
| Reactions total | 2,799 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 04:14 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.
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video 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.
7,744 reactions across 686 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7,744 | 100.0% |
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 725 of the 838 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 7,830 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 838 most recent posts we hold, published 5 August 2026 to 17 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: 13 of 275 posts held from the last 30 days (4.73%) 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).
연간 CAPEX 1t를 하려면 매출이 4t가 나와야 함
❤11
Photo, posted without a caption
❤5
다른 건 모르겠고 ARR이 얼마나 떨어지느냐는 문제인데
* 전망을 하향 조정한 세 가지 이유 1) AI 생태계 전체의 토큰 매출 전망 재조정 - 최첨단 AI 모델 개발사들의 3분기 순증 ARR 증가세가 둔화. 매출로 전체 컴퓨팅 비용을 계속 감당할 수 있는 수준에 맞춰 신규 컴퓨팅 공급 전망을 낮춤. SemiAnalysis는 여전히 이들 개발사의 매출을 시장 컨센서스보다 낙관적으로 보고 있으며, 최첨단 AI를 도입해 높은 투자수익률을 거둘 수 있는 분야도 많다고 본다. 2) 자본시장의 자금 공급 위축 - 채권·대출 투자자와 지분 투자자 모두 AI 인프라 구축에 자금을 대는 데 소극적. 특히 하이퍼스케일러가 임차인으로 확보되지 않은 프로젝트에서 이런 경향이 두드러진다. 그 결과 데이터센터 부지 확보와 전력 인프라 및 건물 개발이 줄어들고, 컴퓨팅 장비를 설치·가동하는 데 쓸 수 있는 전력도…
>>SemiAnalysis, AI 컴퓨팅 수요 전망 대폭 하향…2028년 자본지출 전망 30% 가까이 하향 •SemiAnalysis는 2028년 글로벌 AI 가속기 자본지출 전망을 28% 하향했으며, 2030년 전망은 40% 낮췄음 •2026~2030년 AI 가속기용 실리콘 웨이퍼 출하 면적 누적 전망도 17% 하향했고, 2028년 HBM 수요 전망은 30%, 2030년 전력 수요 전망은 34% 각각 하향. Nvidia가 가장 큰 영향을 받을 것으로 예상되며, 글로벌 실리콘 웨이퍼 출하량 감소분의 66%를 차지하고, 2030년 컴퓨팅 매출 기준 출하 전망은 66% 하향 >SemiAnalysis大幅下修AI算力预测:2028年资本开支预测下调近三成,五年硅片出货面积下调17%,英伟达受冲击最严重 https://wallstreetcn.com/art…
같이 사진 찍으세요
❤4
헐 저 샘 올트먼 봤어요
❤9
샘 올트먼 (OpenAI) 11.16(월) 샌프란시스코 세마포 행사에서 젠슨 황 퇴진 이후에도 AI 업계는 괜찮을 것이라고 말했습니다. 매출과 수요가 매우 강하게 성장하고 있다는 것이 근거입니다. 황의 역할은 특별했다고 평가했지만, 엔비디아 복귀 여부에는 판단할 만큼 알지 못한다고 답했습니다. 앤트로픽 상장으로 OpenAI가 가려지는 것은 걱정거리가 아니라고 했고(2차 보도 기준), 업계가 사람들의 미래 통제권을 강하게 지지해야 한다고 강조했습니다. 같은 날 별도 행사에서는 OpenAI가 시기별로 메모리, 데이터센터 용량 등 서로 다른 부품 제약을 겪어 왔다고 밝혔습니다.
❤8
[리스크 & 경고 신호] 1. 엔비디아 리더십 공백 속 첫 실적 발표 젠슨 황 사임 이후 첫 분기 실적(현지 17일 예정)입니다. 가이던스와 경영 연속성 메시지가 AI 반도체 전체의 방향을 정할 수 있습니다. 2. 기관의 AI 인프라 이탈 3분기 13F 분석에서 데이터센터 종목 전량 매도 펀드 138개, 전력·유틸리티 청산 212개가 확인되었습니다. 관련 종목의 수급 부담이 이어질 수 있습니다. 3. 부품·용량 병목 올트먼이 메모리와 데이터센터 용량 제약을 언급했습니다. 병목은 공급업체에는 호재지만 AI 확장 속도와 비용에는 부담입니다. 4. 초대형 IPO의 유동성 흡수 앤트로픽 IPO가 최대 1.4조 달러 밸류에이션으로 18일 공모가 확정, 19일 상장 예정이라고 보도되었습니다. 기존 AI 대형주에서 자금이 이동할 수 있습니다. 5…
❤1
[트랜스포머 원저자 8인] 아시시 바스와니 (NVIDIA, 前 Essential AI) 금일 발언 없음 노암 샤지어 (OpenAI, 前 Google Gemini) 금일 발언 없음 니키 파르마르 (Anthropic, 前 Essential AI) 금일 발언 없음 야콥 우스코라이트 (Inceptive) 금일 발언 없음 라이온 존스 (Sakana AI) 금일 발언 없음 에이단 고메즈 (Cohere) 금일 발언 없음 우카시 카이저 (OpenAI) 금일 발언 없음 일리아 폴로수킨 (NEAR Protocol) 금일 발언 없음
[기업가/테크 리더] 제이미 다이먼 (JPMorgan) 금일 발언 없음 (참고: 11.12 전후 '아메리칸 드림이 너무 많은 사람에게서 멀어지고 있다'며 관련 이니셔티브를 발표했습니다. 외부 AI 에이전트의 자사 시스템 접근을 허용하지 않겠다는 입장도 재조명되었습니다) 일론 머스크 (Tesla/SpaceX/xAI) 금일 발언 없음 (참고: 11.13 X에 젠슨 황 복귀 청원에 서명하겠다고 올렸습니다. 11.16 테슬라 -2.2%, SpaceX -1.5%였고 예측시장의 SpaceX-테슬라 합병 확률이 62%로 뛰었으나 본인의 당일 발언은 확인되지 않았습니다) 젠슨 황 (前 NVIDIA) 금일 발언 없음 (참고: 11.12 CEO·이사직에서 즉시 사임했고 콜레트 크레스 CFO가 임시 CEO를 맡았습니다. 사임 후 본인 발언은 확인되지 않았습…
❤1
[테크/성장주 전문가] 캐시 우드 (ARK Invest) 금일 발언 없음 (참고: 11.8 CNBC에서 시장이 걱정할 때 오히려 마음이 편하다며 강세장 종료론을 부인했습니다. 젠슨 황 사임 후 엔비디아는 '젠슨 쇼' 이상이라고 평가했고, ARK는 11.12 코어위브 약 1,600만 달러 매수, 팔란티어 약 1,000만 달러 매도가 보도되었습니다) 안드레아스 할보르센 (Viking Global) 금일 발언 없음 차마스 팔리하피티야 (Social Capital/All-In) 금일 발언 없음 (참고: 11.13 All-In에서 젠슨 황 퇴진이 성장률을 50~150bp 깎을 수 있다고 추정했고, 이번 사태가 미 정부의 첨단 칩 통제 강화로 이어질 수 있다고 봤습니다) 마크 앤드리슨 (a16z) 금일 발언 없음 (참고: a16z가 11.13 '…
Showing the 12 most recent of 838 posts we hold for @rafikiresearch. 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.
@rafikiresearch 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.
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 9 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.
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 26 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 35 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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“Rafiki research” (@rafikiresearch), 20,669 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/rafikiresearch.
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.