Channel
@jaysonchart
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,156subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001235262634 |
|---|---|
| Type | Channel |
| Username | @jaysonchart |
| Created | 7 April 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/jaysonchart |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 14:44 | 1,156 | -3 |
| 7 Aug 2026, 09:00 | 1,159 | -1 |
| 6 Aug 2026, 20:31 | 1,160 | no change |
| 6 Aug 2026, 20:25 | 1,160 | first reading |
17 posts held, back to 11 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.
5 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 40.0% | |
| 🖕 | 2 | 40.0% | |
| ❤ | 1 | 20.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 4 of the 17 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 11 October 2025 to 29 June 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.
😆Bithumb 유튜브 구독자 10만명 달성 이벤트 🎁 이벤트 경품 BBQ 황금올리브치킨 + 콜라 1.25L (100명) ✨ 이벤트 참여 방법 1. 빗썸 유튜브 채널을 구독한다. 2. 축하의 메시지를 댓글로 남긴다. 3. 참여 링크를 클릭하고 개인정보 기입, 구독과 댓글 인증 사진을 첨부하면 이벤트 참여 완료!
Signed JAYSONkr
1일 1콜라 받기 https://jtbcevent.com/instant/ 매일 주는 것 같아요 해보니까 콜라 기프티콘 주네요
Signed JAYSONkr
폰을 샀는데 중간중간 고맙다면서 에어드랍도 준 것도 모자라서 폰 가격보다 더 많은 돈을 돌려준다고? $SKR 도 잘 가는데 FIGHT.ID $FIGHT 도 잘 가겠지?
🖕1
Signed JAYSONkr
크리스마스 채널 이벤트 모음 9개채널 연합 https://t.me/tlsrltnf/19834 8개채널 연합 https://t.me/kookookoob/22843 23개채널 연합 https://t.me/legoleecm777/10293 13개채널 연합 https://t.me/cubestudy1557/5230
Signed JAYSONkr
[ 톰 리의 "6-8주" 타임라인의 의미 ] 크립토 시장의 약세는 청산 이벤트(liquidation event) 이후 6-8주로 보고 있습니다. 청산 이벤트(liquidation event)는 2025년 10월 10일의 대규모 청산 사건(플래시 크래시)을 말하는 것이죠. 톰 리는 최근 시장 약세의 원인을 10월 10일 Binance ADL(자동 손실 분배) 버그로 시장에 엄청난 충격을 주었고 그 여파가 지금의 시장 약세의 원인이라고 보고 있습니다. 그럼 6~8주 라는 타임라인을 볼까요? 타임라인 계산: 10월 10일부터 6-8주 - 시작점: 2025년 10월 10일 (liquidation event). - 6주 후: 2025년 11월 21일 (대략 5주 반 지남). - 8주 후: 2025년 12월 5일 (연말 랠리 기대). 결국 …
🖕1
Signed JAYSONkr
받) 10월 한달도 수고하셨습니다.
Signed JAYSONkr
🤪 바이낸스 KITE 런치풀 ✅ 바이낸스에서 AI 지불 블록체인 Kite ($KITE)의 런치풀을 진행합니다. 2일동안 짧게 진행하는 런치풀이네요. 🪙 KITE Launchpool 🟢토큰 이름: Kite ($KITE) 🟢파밍기간 : 11/1 오전 9시 ~ 11/3 오전 9시까지 (KST 기준) 🟢Launchpool 토큰 보상: 150,000,000 $KITE (전체토큰 공급의 1.5%) 🟢BNB 풀 : 127,500,000 KITE 할당 (85%) 🟢FDUSD 풀 : 7,500,000 KITE 할당 (5%) 🟢USDC 풀 : 15,000,000 KITE 할당 (10%) 바이낸스 런치풀페이지 💬 스테이블 코인(FDUSD, USDC) 풀이 합쳐서 15%로 비중이 낮네요. 저는 참전을 안할 예정입니다. BNB 홀딩하시는분들은 꼭 참여하시죠…
Signed JAYSONkr
File, posted without a caption
Signed JAYSONkr
<젠슨 황의 하루 일과표> 1. 오전5시 기상. 2. 5~6시 기상 후 독서 혹은 생각 정리 3. 6시 운동. 근력 운동+유산소 이후 명상 4. 출근 이후 오전 시간대는 가장 중요하고 전략적인 업무에 집중 5. 오후 시간대는 회의, 외부미팅, 파트너/고객 협업 6. 오후 5-6시경 하루 마무리, 성과 점검, 가족과의 휴식, 개인 취미생활(음악, 새로운 기술 등) 7. 오후 6시 이후 업무와 단절. 업무관련 이메일, 메신저 모두 비활성. 가족과 휴식 8. 잠들기 전 하루 묵상(개인적인 반성, 감사할일 등 묵상) #젠슨황 #하루일과표
Signed JAYSONkr
[속보] 젠슨황 깜짝발표(11/1) 내용 공개 대한민국 정부와 민간기업 4곳 (삼성/SK/현대차/네이버)에 GPU 약 25만장 공급 예정 Source : JTBC *엠바고 깬 걸로 추정
Signed JAYSONkr
올해 대전이랑 한화는 정말 야구에 진심인듯👀
Signed JAYSONkr
🔥 NEAR Legion이 깨어난다. «Prepare for ASI» NEAR 시대의 AI 전쟁이 시작됐습니다. 이제 선택의 순간입니다. Rogue ASI(통제 불능의 초지능) vs NEARvana(사용자 소유의 AI 세계) 🦁 Join the NEAR Legion 👉 https://nearlegion.com/ 💠 NEAR Legion은 단순한 커뮤니티가 아닙니다. * $NEAR 홀더들을 위한 전략 허브 * 탈중앙화 AI 구축·수호·실천을 목표로 한 커뮤니티모임 * 미션(퀘스트)을 수행해 SBT(소울바운드 토큰) 으로 신분을 증명 앞으로 NEAR Legion을 통해서 많은 니어프로토콜 관련 프로젝트들이 에어드랍 등 각종 미션이 진행 될 가능성이 매우 높다고 합니다. 💬 슬로건 > “Hold NEAR and Join our Ran…
Signed JAYSONkr
Showing the 12 most recent of 17 posts we hold for @jaysonchart. 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 — 310,917 of 1,160,990entries 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.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“멘탈관리소” (@jaysonchart), 1,156 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/jaysonchart.
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.