Channel
@bubblecheollinternaltrading
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
538subscribers
+164 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003871531877 |
|---|---|
| Type | Channel |
| Username | @bubblecheollinternaltrading |
| Created | Between 1 February 2026 and 20 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/bubblecheollinternaltrading |
Gambling & betting — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 26 Sept 2026, 01:58 | 538 | +23 |
| 13 Sept 2026, 03:21 | 515 | +71 |
| 5 Sept 2026, 10:19 | 444 | +30 |
| 28 Aug 2026, 03:36 | 414 | +10 |
| 20 Aug 2026, 19:24 | 404 | +30 |
| 19 Aug 2026, 19:30 | 374 | first reading |
20 posts held, back to 20 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 19 August 2026. An engagement rate over an empty window would be a number about nothing.
58 reactions across 11 posts, in 2 distinct kinds. The most used accounts for 94.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 55 | 94.8% | |
| 👍 | 3 | 5.17% |
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 12 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 58 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 20 July 2026 to 19 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.
➡️INTERNAL TRADING DATE AND TIME: 20/8/2026 9.00PM 🌹TREASURE SPORTY VERSION #TREASURE01 available members:- jungkyu-18 yoshi-18 jaehyuk-18 asahi-18 doyoung-18 jeongwoo-18 haruto-18 junghwan-18 jihoon-18 hyunsuk-18 buyer list :- NO NEED IT ❌ @nurulfxrisha -set @adiputeri - set @Sallyyy_na - set @minshamaa -set @nrnajlaaaq -set @bluekiys -set @umxiry -set @wtnb_hrt0504 - set @sysfeeya - set @nreensuha - set @kira_…
❤7
updated result ✅ left 2 more slot for sohee, yang tak sempat claim later hold dulu tau, thankyou 🙇🏻♀️
updated result✅
claim sini tau ~ sharp 10.30pm
👍3
preview ya any mistake let me know ^^
➡️INTERNAL TRADING DATE AND TIME: 27/6/2026 10.30PM CORTIS GREENGREEN POB ONLY ➡️weverse mt-1 jm-0 sh-0 kh-0 jh-0 ➡️k4u mt-2 jm-0 sh-0 kh-0 jh-0 ➡️makestar mt-0 jm-0 sh-0 kh-0 jh-0 ➡️aladin mt-0 jm-0 sh-0 kh-0 jh-0 buyer list :- @Nrzira makestar - kh aladin - kh k4u - kh wv - kh @hanznhy wv - sh k4u (2) - jm + mt @littlemissjn wv - jm @liuluv18 wv (2) - @hai_hamburger aladin - jm @shzvvn wv - jh @miramartin wv …
❤5
hi everyone for cortis greengreen pob only will be done at 10.30pm ya is that okay for everyone?
❤17
sorry for late, if ada mistake boleh bagitau 🙇🏻♀️
updated result✅
❤5
thank you for joining will update results as soon as possible
❤4
any questions can ask here 👇
❤1
this are the buyers username yang need to join IT 😶 if your username takde means you got the member you want 🥹 internal trading time and date will be on tomorrow 9PM,thank you for waiting ❤️
❤7
Showing the 12 most recent of 20 posts we hold for @bubblecheollinternaltrading. 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.
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.
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.
@bubblecheollinternaltrading named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“bubblecheoll internal trading” (@bubblecheollinternaltrading), 538 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/bubblecheollinternaltrading.
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.