개귀엽네

Channel
원에서억🥷
@wontobillion
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
905subscribers
-11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002087685593 |
|---|---|
| Type | Channel |
| Username | @wontobillion |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 13 September 2026 |
| On Telegram | t.me/wontobillion |
Topic
Other / unclassifiable — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 4 Sept 2026, 11:16 | 905 | -2 |
| 28 Aug 2026, 12:24 | 907 | -2 |
| 22 Aug 2026, 03:08 | 909 | -1 |
| 15 Aug 2026, 20:15 | 910 | -6 |
| 8 Aug 2026, 01:01 | 916 | no change |
| 7 Aug 2026, 12:33 | 916 | first reading |
Engagement
20 posts held, back to 30 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 24s
- Average length
- 24s
Measured directly from 1 video 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
33 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 81.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 27 | 81.8% | |
| ❤ | 3 | 9.09% | |
| 💩 | 2 | 6.06% | |
| 🔥 | 1 | 3.03% |
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 5 of the 20 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 33 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 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
아씨발 vpn 켜두고 지갑들어갔다가 존나귀찮아죽겠네 왜 vpn을 썻냐는 말은 하지마세요
하닉은 100만원 깨져야 반등장 저점 평단일듯 130만원대가 그런줄 알았는데 다시 다박히는거 보니 안사고싶음 100만원오면 매수할게요 그전까지는 롤딸밥똥 할게요
Fuego 대충 418,000불 (한화 약 6억) 빨고 8시간동안 잠수중 누군가의 20년 연봉 빨았으면 적어도 24시간은 풀타임으로 일하는 성의라도 보이겠다...
지갑 정리하다 생각났는데 이거에드 언제해줌? 펭구피규어
반말하지마라
국민성장펀드 20% 보호막 다 까지고 손실 나기 시작했다고 함 출처
결국 코인에서 하던거 똑같이 하는중 데브buy해서 올리고 매수 다 시켜놓고 알고보니 무한발행 엔딩 바로 중국에서 찍는중
아 ㅋㅋ시 존나웃기네
소액으로 밈코인쫌 해야겠는데
승리요정 미야오 안나 시구
농담 아니라 전포에 있는 남자들 다 이렇게 입음;; 잘생기고 몸좋은 사람들은 참 잘어울리는데 나머지 대다수는 흠 유행따라 모두가 입으니까 전혀 이쁘지 않은 모습
Showing the 12 most recent of 20 posts we hold for @wontobillion. 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
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“원에서억🥷” (@wontobillion), 905 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/wontobillion.
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.