Film & TV — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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.
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 in near-verbatim form on 12 other registered channels. 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)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
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. 29 of the 29 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 195 comparable posts for this entry, running 6 August 2026 to 14 November 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).
Recorded under the keys clone_copy · clone_mutual, last confirmed 14 November 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.
Growth
26 measurements spanning 100 days, net +57. 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 9,113–9,192 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)
Subscribers
Change
14 Nov 2026, 01:20
9,183
+8
8 Nov 2026, 23:59
9,175
+24
5 Nov 2026, 17:06
9,151
-10
2 Nov 2026, 17:44
9,161
-8
31 Oct 2026, 00:40
9,169
+6
28 Oct 2026, 10:05
9,163
+5
23 Oct 2026, 00:46
9,158
+2
20 Oct 2026, 05:08
9,156
+10
17 Oct 2026, 04:16
9,146
+10
13 Oct 2026, 20:10
9,136
+12
7 Oct 2026, 22:16
9,124
-15
1 Oct 2026, 08:59
9,139
+10
16 Sept 2026, 17:18
9,129
-1
12 Sept 2026, 22:58
9,130
-5
8 Sept 2026, 20:20
9,135
-6
3 Sept 2026, 21:35
9,141
-11
31 Aug 2026, 20:05
9,152
-15
28 Aug 2026, 19:47
9,167
+13
26 Aug 2026, 04:43
9,154
+3
22 Aug 2026, 20:34
9,151
first reading
Engagement
601 posts held, back to 6 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 55 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
11.8%
avg views ÷ 9,183 subscribers
Avg views / post
1,080
267 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
267
of 601 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 14 November 2026
Posts held
601 (6 August 2026 – 14 November 2026)
Views total
289,119
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
14 Nov 2026, 12:58 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.
What this channel posts
Photos
≈16,300
Videos
≈2,360
Links
≈9,300
Lifetime counters from Telegram’s own channel header, read 14 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.
Video runtime
29m 50s
Average length
25s
Measured directly from 72 videos 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.
Recent posts
Telegram’s own ‘edited’ marker: 47 of 267 posts held from the last 30 days (17.6%) 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).
"나는 시합이 잡히면 땅 먼저 계약을 했어. 그 당시 땅들이 쌌네. 수원 화성 안산 이런 데는 땅이 쌌어. 은퇴할 무렵에 전체 사 놓은데 보니까 28군데가 있대. 돈으로 환산하면 90억 정도 되겠더라고. 90년도에. (여기서부터 반전..ㅠㅠ) 근데 이게 그릇이 있는 거 같아. 은퇴하고 2년동안 놀다보니까 같이 놀아줄 사람이 없어. 그래서 내가 술집을 했어. 술도 못 먹으면서. 거기서 내가 잘못된거야. 한두달은 잘 했는데 언젠가부터 외상을 받기 시작하고 술값이 쌓이면 어음을 가져오더라고. 300만원 술값이면 1000만원 어음을 받고 700만원 현금을 내주고. 그러고 두세달 뒤에 그 어음이 잘못되서 돌아오더라고. 부도가 난거지. 나는 갖고 있으면 다 돈인 줄 알았어. 그냥 종이더라고. 또 사악 꼬시는 거야. 3억만 투자하면 3개월 뒤에 원금을 주…
“저는 많이 오른 동네를 사라고 말씀드려요. 보통 비싼 게 더 많이 오르기 때문에 이왕이면 살 수 있는 것 중에 제일 좋은 것을 사라고 말씀드립니다. 상승장이 오면 더 가고 하락장이 오면 어차피 다 같이 빠지기 때문에..“
- 송희구 작가 (서울 자가에 대기업 다니는 김부장 이야기)
https://youtube.com/shorts/JO0P3y_Q5Yg?si=scLhCy7UCj0Anau7
>>트럼프, 이란에 대한 군사 공격 잠정 중단 검토 (로이터)
•소식통에 따르면, 미국 대통령 트럼프는 최근 고위 보좌관들에게 미국이 이란이나 예멘 후티 반군으로부터 새로운 도발을 받지 않을 경우 이란에 대한 군사 공격을 잠정 중단할 가능성이 있다고 밝힘
>【报道:特朗普考虑暂缓对伊朗军事打击】知情人士透露,美国总统特朗普近日向高级顾问表示,如果美国未受到来自伊朗或也门胡塞武装的任何新挑衅,他可能会暂缓对伊朗采取军事打击。(路透) (来自华尔街见闻)
[삼양식품 CAPA 로드맵 및 주요 Q&A ]
현재 : 약 29억 개
자싱 : 약 11억 개
베트남 (8개 라인 기준) : 약 11억 개
TOTAL : 약 51억 개
1. 자싱은 현 캐파 대비 약 40% 추가임.
2. 한국 생산 29억 개 중 약 30%가 이미 중국향이고, 이 물량이 점진적으로 자싱으로 이관됨.
3. 이관만으로 자싱 11억 개의 약 80%가 채워짐.
4. 결과적으로 중국의 실질 캐파 증분은 약 10%이고, 약 30%는 ASP가 높은 미국·유럽향으로 재배치됨.
5. 베트남은 2029년 이후 유럽 성장을 담당함. 자싱 발표 후 2025~26년에 중국 성장을 위한 전략적 결정을 했던 것처럼, 2027~28년에는 유럽 거래선 발굴에 집중할 예정임.
6. 한국은 미주 거래선 개발과 물량 대응을 담당함.
7. 중기적으로 중국향 생산 증…
이 뉴스는 이거랑 같이보면 좀 쎼하죠.
엘리자베스 워런은 순환금융을 08년같은 거라고 봐서 건드릴 가능성이 높다
https://finance.yahoo.com/economy/policy/articles/elizabeth-warren-sees-2008-style-033022251.html
Showing the 12 most recent of 601 posts we hold for @pengmeup. 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.
Posts edited after publishing
@pengmeup edited 2 posts 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.
First edit seen
8 August 2026
Most recent edit
3 November 2026
Posts recorded as deleted after publishing
We recorded 1 post on @pengmeup 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.
First seen missing
22 August 2026
Most recent seen missing
22 August 2026
Median time before seen missing
33 hours
Seen missing in the last 30 days
0
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 4 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.
Appears in Telegram’s recommendations for other channels
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.
재야의 고수들 @gaoshoukorea · 41,185 Telegram ranks this channel #69 of 90 here — alongside 89 others — read 2 September 2026
선진짱 주식공부방 @sunstudy1111 · 55,218 Telegram ranks this channel #73 of 89 here — alongside 88 others — read 2 September 2026
YM리서치 @ym_research · 39,801 Telegram ranks this channel #78 of 89 here — alongside 88 others — read 2 September 2026
Yeouido Lab_여의도 톺아보기 @Yeouido_Lab · 43,450 Telegram ranks this channel #78 of 90 here — alongside 89 others — read 2 September 2026
피카츄 아저씨⚡️ @pikachu_aje · 24,917 Telegram ranks this channel #83 of 91 here — alongside 90 others — read 14 September 2026
조기주식회 공부방 @EarlyStock1 · 24,359 Telegram ranks this channel #86 of 91 here — alongside 90 others — read 16 September 2026
습관이 부자를 만든다. 🧘 @habit4117 · 28,295 Telegram ranks this channel #87 of 87 here — alongside 86 others — read 10 September 2026
This channel appears in 8 seed channels' Telegram-generated recommendation lists in total, of which the 7 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 14 November 2026 — this
entry's latest reading, not the date you are reading this.
“힙한 펭미업의 1인칭 시점” (@pengmeup), 9,183 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/pengmeup.
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.