Channel
@sjpark_sobi
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
2,778subscribers
+18 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001758893265 |
|---|---|
| Type | Channel |
| Username | @sjpark_sobi |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/sjpark_sobi |
Other / unclassifiable — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 89% 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.
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.
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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @sjpark_sobi/1559 · this entry5 Aug 2026, 22:33 UTC | @KiwoomResearch/236935 Aug 2026, 22:33 UTC | 1.00 | under a minute |
| @sjpark_sobi/1560 · this entry5 Aug 2026, 22:34 UTC | @KiwoomResearch/236945 Aug 2026, 22:35 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @KiwoomResearch | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–0) |
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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 23 comparable posts for this entry, running 22 June 2026 to 6 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.
Across the whole group of 3, the earliest publisher we hold is @KiwoomResearch. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 06:38 | 2,778 | +11 |
| 12 Aug 2026, 06:26 | 2,767 | +9 |
| 9 Aug 2026, 03:54 | 2,758 | -2 |
| 6 Aug 2026, 05:17 | 2,760 | no change |
| 6 Aug 2026, 02:48 | 2,760 | first reading |
23 posts held, back to 22 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 2 pagesof 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 23 (22 June 2026 – 6 August 2026) |
| Views total | 18,494 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:11 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.
★ CJ프레시웨이(051500): 식봄 GMV 고성장으로 매출 성장 가속화 전망 [키움 음식료/유통 박상준] 1) 2분기 연결기준 영업이익 235억원으로 당사 기대치 부합 - 연결기준 매출 YoY +4.5% 증가 - 급식사업 성장 둔화 불구(+3% YoY), 온라인 사업 성장(521억원, +51% YoY)과 식품 원료 부문 고성장(+14% YoY) 등에 기인 - 연결기준 영업이익 YoY -14% 감소 - 마켓보로 연결 편입에 따른 영업손실, 온라인 사업 확대를위한 광고/판촉비 확대로 인해, 전사 영업이익률 하락(-0.6%p YoY) 2) 식봄 GMV 고성장으로 매출 성장 가속화 전망 - 2분기 식봄 GMV는 YoY +30.5% 증가한 861억원, 상품 SKU와 통합배송 SKU도 각각 +37%, +117% 증가 - 식봄 신규고객 유입 확대에…
★ KT&G(033780): 26~27년 DPS 전망치 상향 조정 [키움 음식료/유통 박상준] 1) 2분기 영업이익 4,145억원으로 시장 컨센서스 부합 - 담배: 국내 판매량 증가, 해외 궐련 판가 인상 및 판매량 증가, 달러 강세 등에 힘입어, 영업이익이 YoY +19% 증가 - 건기식: 국내 고수익 채널 중심의 매출 확대에 힘입어, 영업이익이 크게 개선 - 부동산: 안양 등 중소형 개발사업 매출 증가에 따라 영업이익이 증가 2) 26~27년 DPS 전망치를 각각 7,600원, 8,600원으로 상향 - KT&G는 연간 매출액과 영업이익 증가율 가이던스를 상향 조정하며 올해 반기 주당배당금도 전년대비 600원 상향한 2,000원으로 결정 - 동사는 영업현금흐름, Capex 축소, 비핵심자산 유동화 등을 통해 마련된 재원을 바탕으로, 올해…
★ BGF리테일(282330): 2분기도 시장 기대치 상회 [키움 음식료/유통 박상준] 1) 2분기 영업이익 849억원으로 시장 컨센서스 상회 - 내수 소비경기 호조로 편의점 동일점 매출이 증가(전체 +4.2%,담배제외 +5.3%) - 점포 순증 둔화와 상품 믹스 개선 등에 힘입어, 매출 증가에 따른 영업레버리지 효과가 예상 보다 강하게 나타난 것으로 판단 - 주요 종속기업의 영업이익은 자회사 로지스의 일회성 비용 반영 등의 영향으로 전년동기 대비 -55억 감소 2) 날씨 영향은 단기 변수이나, 안정적 이익 증가는 무난 - BGF리테일의 3분기 연결기준 영업이익은 1,062억원(+9% YoY)으로 전망 - 2분기 매출 호조를 감안한다면, 3분기에도 양호한 동일점 성장률(+2% 전망)이 기대 - 중기적으로 경쟁 상황이 다소 완화되고 있는 점…
★ 롯데칠성(005300): 원가 상승 부담 방어 중 [키움 음식료/유통 박상준] 1) 2분기 연결기준 영업이익 558억원(-10.5% YoY)으로 당사 기대치 부합 - 별도기준 매출 YoY +2% 증가. 제로탄산, 새로, RTD 주류 중심의 판매량 성장에 힘입어 매출 성장. - 별도기준 영업이익률은 4.0%로 YoY +0.1%p 개선. 포장재/물류비 상승 부담에도 고수익성 제품 비중 확대와 고정비 효율화와 적자 사업 철수(생맥주)로 수익성 방어. - 글로벌 사업은 중동 전쟁 여파에 따른 포장재/물류비 상승 부담 심화로 전년동기 대비 감익(-97억원 YoY) 2) 원가 상승 부담 방어 전망 - 포장재/물류비와 환율 상승에 따른 원가 상승 부담을 주력 제품 가격 인상과 인건비 등 고정비 효율화를 통해 방어할 계획 - 3Q부터 국내 주력 제품…
★ 현대백화점(069960): 눈높이 하향 조정은 필요 [키움 음식료/유통 박상준] 1) 2분기 영업이익 793억원으로 시장 기대치 하회 - 6~7월 주요 가전 브랜드 행사 영향에 따른 패션 매출 둔화로 백화점의 수익성이 당사 기대치를 하회(2Q 기존점 +17%, 패션+7%) - 백화점: 영업이익은 YoY +408억원 증가, 감가상각비 감소와 보유세 증가 영향을 제외 시 기존점 매출 성장에 따른 영업이익 증가효과는 343억원 수준(+49% YoY)으로 추산 - 면세점: 인천공항 DF2 권역이 조기에 흑자를 달성하면서, 전분기 대비 이익이 증가 - 지누스: 관세환급금에 따른 일회성 수익 141억원을 제외한다면, 체화재고 소진에 따른 비용 증가 부담으로 인해 전분기 대비 영업적자가 107억원 확대 2) 3분기 영업이익 전망치를 898억원으로 …
★ CJ(001040): 성장세는 유효하나, 수익성 하락 우려는 부담 [키움 음식료/유통 박상준] 1) 2분기 영업이익 5,956억원으로 시장 기대치 하회 전망 - 올리브영은 인바운드와 온라인 중심의 매출 성장세에 신사업(올리브베러/미국) 성장 모멘텀이 붙고, - 푸드빌은 미국 중심의 글로벌 매출 성장이 지속되면서, 매출 성장 흐름은 1분기와 유사할 것으로 판단 - 다만, 올리브영과 푸드빌 모두 중장기 외형 성장을 위한 투자 증가로 수익성이 전반적으로 약한 모습을 보일 전망 2) 인바운드 성장 유효하나, 수익성 하락 우려는 부담 요인 - 올리브영: 올해 2분기 K 콘텐츠에 대한 관심도 증가 및 한일령 반사수혜 영향으로 인바운드 중심의 매출 성장세는 가시성 높은 편(2Q 국내 입국자 수 +20% YoY) - 미국 올리브영과 올리브베러 등 신…
★ 키움 음식료 Weekly (8/3) [키움 음식료/유통 박상준] ★ Weekly News & Comments 1) 농심, 용기라면 출고가 인상(iii.ad/0e661b) - 농심이 8월 1일부터 용기면 평균 6%·스낵 5.5% 인상하며 식품업계 가격 인상 대열에 합류 - CJ제일제당 8%·오뚜기·롯데칠성 5.3% 등 주요 식품사 가격 인상이 줄이어 업계 전반으로 확산 - 원부자재·포장재 가격 상승과 고환율 지속에 따른 원가 부담 누적이 공통 인상 배경 2) 롯데웰푸드, 인도 롯데초코파이 4번째 생산라인 가동(iii.ad/b14a36) - 300억원 투자한 인도 로탁 공장 제4라인 본격 가동으로 연간 생산 캐파 약 33% 증가 - 초코파이 시장점유율 70% 이상·3년 연평균 20% 성장 속 올해 매출도 YoY…
★ 음식료 수출입 통계 [키움 음식료/유통 박상준] ★ 음식료 수출입 통계 Update(8/1, 수리일 기준) 1) 7월 일평균 수출입금액 YoY (25/07/01~31 vs 26/07/01~31) - 담배 수출: 일본 제외 +60%, UAE +136%, 신시장(UAE 外) -10% - 라면 수출: 전체 +15%, 중국 -14%, 미국 +39% ★ 관세청 수출입 데이터의 엑셀 파일이 필요하신 분은 문자 부탁 드립니다.
★ 음식료/유통 2Q26 실적발표 일정 업데이트(+주요 해외기업) - 7/28(화): 코카콜라(음료) - 7/29(수): 스타벅스(음료) - 7/30(목): BUD APAC(오비맥주 모회사), 아마존(이커머스) - 7/31(금): 호텔신라(예상), 도요수산(라면) - 8/4(화): 닛신식품(라면), 쿠팡(이커머스) - 8/5(수): 롯데칠성(14시 컨콜) - 8/6(목): KT&G(16시 컨콜), CJ프레시웨이, BGF리테일(예상), GS리테일(예상), 현대백화점(예상) - 8/7(금): 롯데웰푸드(16시 컨콜) - 8/11(화): CJ제일제당(9시반 컨콜), 신세계(예상) - 8/12(수): 이마트(예상) - 8/14(금): 농심(예상) - 8/20(목): 월마트(할인점)
★ 필립모리스 (PM.US): 담배는 너무 잘 팔지만 [키움 음식료/유통 박상준] 1) SFP, 궐련담배 모두 견고하게 성장 중 - 필립모리스의 2Q26 매출액은 $11.2B(YoY +10.4%, 컨센서스대비 +1.8%) 기록 - 조정 EPS 는 $2.20(YoY +15.2%, 컨센서스 대비 +7.6%)을 기록 - 궐련담배는 가격과 물량 모두 증가하며 실적 서프라이즈를 주도(물량 YoY +1.1%, ASP YoY +10.0%) - 인터내셔널 SFP도 물량 기준 YoY +8.0% 성장하며 매출 비중 확대 지속 2) 본업 성장은 양호하지만 주가, 매크로 부담 존재 - 연간 Organic 가이던스는 유지, 달러 기준(환율 노출) EPS 에 반영되는 환율 기여분은 +$0.20 에서 +$0.15 로 하향 조정 - 7 월 기준 달러인덱스는 연초 대비…
★ 음식료 수출입 통계 [키움 음식료/유통 박상준] ★ 음식료 수출입 통계 Update(7/21, 수리일 기준) 1) 7월 일평균 수출입금액 YoY (25/07/01~31 vs 26/07/01~20) - 담배 수출: 일본 제외 +9%, UAE +31%, 신시장(UAE 外) -12% - 라면 수출: 전체 +11%, 중국 -19%, 미국 +33% ★ 관세청 수출입 데이터의 엑셀 파일이 필요하신 분은 문자 부탁 드립니다.
★ 음식료 2Q26 Preview: 부정적인 외부 변수 완화 중 [키움 음식료/유통 박상준] 1) 2분기, 양호한 매출 대비 수익성은 약할 듯 - 2분기 매출은 내수 소비 심리 회복과 글로벌 매출 성장에 힘입어, 전반적으로 양호한 흐름을 보일 전망 - 다만, 중동 전쟁 영향에 따른 비용 상승 부담으로, 전사 수익성 개선은 매출 증가 대비 약할 것으로 판단 - 특히, 중국을 제외한 아시아 지역 중심으로 수익성이 부진할 것으로 판단 - 한편, 글로벌 매출은 여전히 대형 3社(KT&G/삼양식품/오리온)의 성장세가 돋보이나, 농심과 롯데웰푸드의 성장세가 1분기 대비 개선될 것으로 전망 2) 업종을 둘러싼 부정적 요인은 점차 완화될 전망 - 중동 전쟁에 따른 비용 상승 부담과 추석 시점 차이로 인해, 3Q는 전사 영업이익의 YoY 개선 강도가 예상…
Showing the 12 most recent of 23 posts we hold for @sjpark_sobi. 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 — 451,164 of 1,481,243entries 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.
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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“키움 음식료/유통 박상준” (@sjpark_sobi), 2,778 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/sjpark_sobi.
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.