![Telegram profile photo for [토큰뷰] TokenView](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMzIwIiBoZWlnaHQ9IjMyMCIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSIgdmlld0JveD0iMCAwIDEwMCAxMDAiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI%2BPGRlZnM%2BPGxpbmVhckdyYWRpZW50IGlkPSJnIiB4MT0iMCUiIHgyPSIwJSIgeTE9IjAlIiB5Mj0iMTAwJSI%2BPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iI2ZmY2Q2YSIvPjxzdG9wIG9mZnNldD0iMTAwJSIgc3RvcC1jb2xvcj0iI2ZmYTg1YyIvPjwvbGluZWFyR3JhZGllbnQ%2BPC9kZWZzPjxzdHlsZT50ZXh0e2ZvbnQ6NjAwIDQ0cHggLWFwcGxlLXN5c3RlbSxCbGlua01hY1N5c3RlbUZvbnQsJ1NlZ29lIFVJJyxSb2JvdG8sSGVsdmV0aWNhLEFyaWFsLHNhbnMtc2VyaWYsJ0FwcGxlIENvbG9yIEVtb2ppJywnU2Vnb2UgVUkgRW1vamknLCdTZWdvZSBVSSBTeW1ib2wnOy13ZWJraXQtdXNlci1zZWxlY3Q6bm9uZTt1c2VyLXNlbGVjdDpub25lfTwvc3R5bGU%2BPHJlY3Qgd2lkdGg9IjEwMCIgaGVpZ2h0PSIxMDAiIGZpbGw9InVybCgjZykiLz48dGV4dCB0ZXh0LWFuY2hvcj0ibWlkZGxlIiB4PSI1MCIgeT0iNjYiIGZpbGw9IiNmZmYiPu2GoFQ8L3RleHQ%2BPC9zdmc%2B)
Channel
@tokenview7
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,866subscribers
-37 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001449082468 |
|---|---|
| Type | Channel |
| Username | @tokenview7 |
| Created | 23 April 2019 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 18 September 2026 |
| On Telegram | t.me/tokenview7 |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 09:16 | 1,866 | -1 |
| 10 Sept 2026, 22:41 | 1,867 | -5 |
| 1 Sept 2026, 21:34 | 1,872 | -10 |
| 29 Aug 2026, 14:48 | 1,882 | -5 |
| 26 Aug 2026, 14:38 | 1,887 | -3 |
| 23 Aug 2026, 15:05 | 1,890 | -2 |
| 20 Aug 2026, 06:35 | 1,892 | -2 |
| 17 Aug 2026, 10:04 | 1,894 | -1 |
| 13 Aug 2026, 14:38 | 1,895 | -4 |
| 10 Aug 2026, 11:33 | 1,899 | -4 |
| 6 Aug 2026, 11:31 | 1,903 | no change |
| 6 Aug 2026, 09:49 | 1,903 | first reading |
2 posts held, back to 23 April 2019 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pages 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 2 posts for this entry, the most recent from 3 September 2025. An engagement rate over an empty window would be a number about nothing.
예측 시장이 도박이 아닌 이유 예측 시장을 처음 보는 대부분의 사람들은 이 시장이 그저 새로운 옷을 입은 스포츠 베팅이라고 생각한다. 불확실한 결과에 돈을 건다. 맞으면 이기고, 틀리면 진다. 스포츠 경기에 베팅하는 것과 무엇이 다르겠는가? 음... 차이점은 점성술과 천문학의 차이와 같다 언뜻 보면 비슷해 보일 수 있지만, 목적이 완전히 다르다. 스포츠 베팅은 오락을 위해 설계되었다. 스포츠 베팅 사이트에서 보는 배당률은 현실의 예측이 아니다. 하우스가 손실을 보지 않도록 양쪽에 돈의 균형을 맞추도록 설계되었다. 너무 많은 사람들이 한 팀에 베팅하면 배당률이 바뀐다. "확률"은 그저 연극이다. 현실 세계에 대해 아무것도 말해주지 않는다. 예측 시장은 진실을 위해 설계되었다. 63센트에 거래되는 계약은 시장 전체가 그 결과…
Channel created
Showing the 2 most recent of 2 posts we hold for @tokenview7. 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.
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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“[토큰뷰] TokenView” (@tokenview7), 1,866 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/tokenview7.
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.