📩문의 : @yunlog
📣주제 : 코인 l 공모주 l 재테크 정보
📌채널 : https://linktr.ee/yun_log
본 채널은 투자 권유 목적이 아닌
정보 공유 및 학습용 채널입니다.
모든 투자 판단과 책임은 개인에게 있으며,
본 채널은 어떠한 수익도 보장하지 않습니다.
광고성 콘텐츠 및 KOL 활동 관련 게시물은 하단에 #KOL 태그가 기재됩니다.
Created
Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
Crypto & trading — 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 96% 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.
Growth
61 measurements spanning 93 days, net +523. 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 10,112–11,135 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)
Subscribers
Change
6 Nov 2026, 15:37
10,753
-11
5 Nov 2026, 13:31
10,764
-1
4 Nov 2026, 16:37
10,765
-4
3 Nov 2026, 16:09
10,769
-10
2 Nov 2026, 12:49
10,779
-3
31 Oct 2026, 13:04
10,782
-13
30 Oct 2026, 09:46
10,795
-2
29 Oct 2026, 11:06
10,797
-3
28 Oct 2026, 11:21
10,800
-6
27 Oct 2026, 13:35
10,806
-7
26 Oct 2026, 15:01
10,813
-6
25 Oct 2026, 15:37
10,819
-3
24 Oct 2026, 18:48
10,822
-2
23 Oct 2026, 18:39
10,824
-5
21 Oct 2026, 20:55
10,829
-8
20 Oct 2026, 15:54
10,837
-15
19 Oct 2026, 16:31
10,852
-10
18 Oct 2026, 16:18
10,862
-2
17 Oct 2026, 14:30
10,864
-11
16 Oct 2026, 11:08
10,875
first reading
Engagement
249 posts held, back to 4 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 46 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
7.52%
avg views ÷ 10,753 subscribers
Avg views / post
808
49 posts measured
Reaction rate
0.471%
reactions ÷ views · ER floor
Posts in window
49
of 249 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 43 of 49 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 6 November 2026
Posts held
249 (4 August 2026 – 6 November 2026)
Views total
39,602
Reactions total
172
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Nov 2026, 20:46 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
≈11,300
Videos
≈189
Links
≈7,110
Lifetime counters from Telegram’s own channel header, read 6 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
1m 12s
Average length
24s
Measured directly from 3 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.
Reaction mix
1,770 reactions across 212 posts, in 6 distinct kinds. The most used accounts for 74.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5429277624981538430
1,314
74.2%
custom 5429309601013056582
242
13.7%
❤
158
8.93%
👍
28
1.58%
👏
19
1.07%
🔥
9
0.508%
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 231 of the 249 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 1,918 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 249 most recent posts we hold, published 4 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.
Recent posts
Telegram’s own ‘edited’ marker: 3 of 49 posts held from the last 30 days (6.12%) 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).
✅X-Agent, AI 에이전트 보안 강화 계획 공개
AI가 직접 지갑을 관리하고 결제하는 시대를 대비해 X-Agent가 보안 강화 조치를 공개했는데요
최근 바이낸스 보안 사고를 계기로 단순히 개인키를 안전하게 보관하는 것뿐 아니라, 지갑 권한과 자금 이동까지 통제하는 것이 중요하다고 강조했습니다
✅현재 적용된 조치
- 업무용 개인키 구글 클라우드로 이전
- 클라우드플레어 방화벽 적용 및 외부 서버 접근 차단
- 매일 취약점 점검 및 주간 AI 보조 보안 검토
✅앞으로 추진할 계획
- 중요 작업에 다중서명(Multi-Sig) 도입
- AI 에이전트별 지출 한도 및 자금 분리
- 결제 대상·금액·네트워크 사전 검증
- 외부 플러그인 및 MCP 연결 보안 점검
- ZK를 활용한 예산 검증 방식 연구
특히 AI에게 무제한으로 지갑 권한을 …
😳미드나잇 2026 리캡 밋업에 참석했습니다.
미드나잇 나이트포스 1기 활동을 하면서 $NIGHT 관련 공지사항도 채널에 올리고 여러 오프라인 이벤트도 진행했는데 돌이켜보면 $NIGHT의 여러 이벤트에 참여했던 것 같습니다.
근처에 있으신 분들은 아직 늦지 않았으니 오셔서 같이 이야기 나누어보아요~~
https://t.me/midnight_kor/219
지금 고민 중인 것들.
1)전닉, 지금부터 사야 하나.
2)속슬은 왜 이렇게 빠지지. 인간적으로 반등 한 번은 주지 않으려나 싶은데, 이 소리를 70달러부터 하고 있었음.
3)HYPE도 슬슬 내려오는데 여기서 혼자 올리는 LIT은 뭐지. 미국 거래소 승인 관련해서 뒤에서 뭔가 이야기가 돌고 있나 싶고.
4)하닉 펀비는 존나 맛있겠다는 생각이 듦.
ADR이랑 본주 갭도 50%네? 이걸 안 들어가?
근데 막상 갭 먹으러 들어가자니 펀비가 존나 건달임.
5)SPY·QQQ는 내 기준 지금부터도 안 사면 병신존이다 싶음.
6)여기서 포폴 없으면 뒤져야 된다 싶을 정도라, 풀시드 현금인 친구들 붙잡고 30%는 매수 들어가라고 존나 얘기하고 있음.
[거래] 콜렉터크립트(CARDS) 신규 거래지원 안내 (KRW, BTC, USDT 마켓)
🔗 공지사항 확인하기
Showing the 12 most recent of 249 posts we hold for @yunlog_official. 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
@yunlog_official 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
15 August 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 60 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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 1 registered channel — 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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@yunlog_official named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@riftboundkr named in 1 post, 12 August 2026 – 12 August 2026 · confirmed gone 12 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@heyelsa_korea named in 1 post, 27 August 2026 – 27 August 2026
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.
에어드랍ATM @Bounty_ATM · 25,834 Telegram ranks this channel #11 of 79 here — alongside 78 others — read 14 September 2026
에어드랍코리아 (Airdropkorea) @airdrop_kor · 21,319 Telegram ranks this channel #12 of 84 here — alongside 83 others — read 24 September 2026
폐지줍기 연구소 @airdr0p_lab · 20,494 Telegram ranks this channel #13 of 88 here — alongside 87 others — read 26 September 2026
잼민123🦅 @mujammin123 · 25,811 Telegram ranks this channel #19 of 86 here — alongside 85 others — read 13 September 2026
🔥요블이 세상살이🔥 @yobeullyANN · 22,294 Telegram ranks this channel #22 of 85 here — alongside 84 others — read 21 September 2026
코인같이투자 정보 에어드랍🦋 @WeCryptoTogether · 48,256 Telegram ranks this channel #25 of 90 here — alongside 89 others — read 25 August 2026
마샬 공유방 2.0 @marshallog · 21,403 Telegram ranks this channel #30 of 81 here — alongside 80 others — read 22 September 2026
취미생활방📮 @enjoymyhobby · 48,940 Telegram ranks this channel #31 of 92 here — alongside 91 others — read 25 August 2026
Gram 🇰🇷 @toncoin_kr · 23,006 Telegram ranks this channel #39 of 88 here — alongside 87 others — read 30 September 2026
Units.Network Announcements @unitsnews · 663,540 Telegram ranks this channel #53 of 85 here — alongside 84 others — read 15 August 2026
변창호 코인사관학교 BCH @BChoSN · 26,355 Telegram ranks this channel #63 of 88 here — alongside 87 others — read 15 September 2026
갓물주 (코인정보, 돈되는거) @godmulzoo · 22,087 Telegram ranks this channel #65 of 81 here — alongside 80 others — read 19 September 2026
신기술은 돈이 된다 공지방 @tlsrltnf · 22,416 Telegram ranks this channel #67 of 86 here — alongside 85 others — read 20 September 2026
졸업준비위원회🎓 @officialunivercityofcrypto · 22,709 Telegram ranks this channel #68 of 86 here — alongside 85 others — read 19 September 2026
텔레그램 코인 방,채널 - CEN @emperorcoin · 35,592 Telegram ranks this channel #73 of 91 here — alongside 90 others — read 19 August 2026
코인 갤러리(Coin gallery) @dogeland01 · 20,946 Telegram ranks this channel #75 of 85 here — alongside 84 others — read 24 September 2026
30대에 은퇴번복한 머피 @murphybus · 19,930 Telegram ranks this channel #76 of 88 here — alongside 87 others — read 28 September 2026
DeFi 농부 👨🏻🌾 조선생 @BSC_Farmer_KR · 20,297 Telegram ranks this channel #76 of 88 here — alongside 87 others — read 26 September 2026
This channel appears in 18 seed channels' Telegram-generated recommendation lists in total. 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 6 November 2026 — this
entry's latest reading, not the date you are reading this.
“윤로그 공지방” (@yunlog_official), 10,753 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/yunlog_official.
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.