Sticker, posted without a caption

Channel
진토리
@Jinstori
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,212subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001817662225 |
|---|---|
| Type | Channel |
| Username | @Jinstori |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/Jinstori |
Topic
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 15:05 | 1,212 | +3 |
| 28 Aug 2026, 08:43 | 1,209 | +1 |
| 25 Aug 2026, 07:43 | 1,208 | -1 |
| 22 Aug 2026, 16:23 | 1,209 | +3 |
| 19 Aug 2026, 03:25 | 1,206 | -5 |
| 15 Aug 2026, 17:45 | 1,211 | -1 |
| 12 Aug 2026, 02:16 | 1,212 | -2 |
| 8 Aug 2026, 23:51 | 1,214 | +1 |
| 8 Aug 2026, 09:34 | 1,213 | first reading |
Engagement
18 posts held, back to 26 July 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 1 page of 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 18 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 1 of the 18 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 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 26 July 2026 to 7 August 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
신세경이 너도 역사속으로 가는거야?..
업비트(Upbit) 공지 신세틱스(SNX) 거래 유의 종목 지정 안내 2026-08-07 16:30:06
Wow
[거래] 봉크(BONK) 거래지원 종료 안내 (9/7 15:00) 🔗 공지사항 확인하기
캐시캣 차트를 보고 다시 살아난거 보고 충격먹음.. 서양형님들이 나름대로 자기들 파이먹으려고 판 열심히 짜는거 같은데 창펑이형 트위터 잘 주시해야겠다
진짜 되네 온체인에 넣어둔 자금이 거의 없어서 많이 매수하진 못했지만, 그래도 오랜만에 꿈을 파는 시장다운 흐름이 나온 것 같네요. 아무쪼록 라이터→ 비트스탬프→ 로빈후드로 이어지는 이 흐름은 한 번쯤 기억해둘 만하다고 생각합니다.
내가 마켓메이커라면 지금 터지는 호재로 거래량 유입되는 시점 일부 매집한 현물을 던지고 숏 전환을 시작하지 않을까? 장기적으로 데리고 갈 코인이라면 떨어질꺼고 그냥 화재를 만들고싶으면 말도안되는 상승을 하지않을까 모르겠다 옛날 네이로가 되려나 제일무서운건 일론트위터에 상호작용되었을때?.. 허허허 아몰랑 팔았으니 안보고싶다
❤1
Sticker, posted without a caption
https://x.com/Aster_DEX/status/2084713073001242650?s=20 ㅅ1 발. .팔았는데 호재 나오네 시~벌탱 바낸 본진가겠누
새벽에 오르기전에 망상? 상상을 좀 해봤음 기글은 바낸 스팟에도 들어와있어서 어떻게 올릴지 궁금함
기글 134개랑 선물 두배롱 포지션 잡아서 데리고 가고있음 60원까지가주면 땡큐
Showing the 12 most recent of 18 posts we hold for @Jinstori. 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.
Forward network
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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“진토리” (@Jinstori), 1,212 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Jinstori.
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.