[инст] #bts КЬЮТ 😭
custom 5262649060153634268117custom 535528111090749390138custom 534133220818133667416

Channel
@ipgb_taekook
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,276subscribers
-38 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001880845069 |
|---|---|
| Type | Channel |
| Username | @ipgb_taekook |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/ipgb_taekook |
Music — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 18 Sept 2026, 18:19 | 3,276 | -4 |
| 14 Sept 2026, 17:39 | 3,280 | -6 |
| 11 Sept 2026, 07:21 | 3,286 | +4 |
| 6 Sept 2026, 08:38 | 3,282 | -4 |
| 30 Aug 2026, 02:58 | 3,286 | -7 |
| 27 Aug 2026, 00:53 | 3,293 | -4 |
| 24 Aug 2026, 00:04 | 3,297 | -10 |
| 20 Aug 2026, 06:24 | 3,307 | -7 |
| 16 Aug 2026, 19:43 | 3,314 | +1 |
| 13 Aug 2026, 02:08 | 3,313 | +4 |
| 10 Aug 2026, 08:37 | 3,309 | -7 |
| 7 Aug 2026, 14:54 | 3,316 | +2 |
| 6 Aug 2026, 22:01 | 3,314 | first reading |
9 posts held, back to 5 August 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 3 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 9 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
1,494 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 31.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5355281110907493901 | 465 | 31.1% | |
| custom 5269494168576603603 | 279 | 18.7% | |
| custom 5341485529923870338 | 241 | 16.1% | |
| custom 5262649060153634268 | 207 | 13.9% | |
| custom 5249095109735103154 | 151 | 10.1% | |
| custom 5341332208181336674 | 91 | 6.09% | |
| custom 5341442356912610137 | 59 | 3.95% | |
| custom 5336993024197011561 | 1 | 0.067% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 9 of the 9 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,494 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 5 August 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.
[инст] #bts КЬЮТ 😭
custom 5262649060153634268117custom 535528111090749390138custom 534133220818133667416
[инст] #jungkook полное видео 🤭
custom 526949416857660360388custom 535528111090749390127custom 534144235691261013720custom 52490951097351031548custom 52626490601536342683custom 53413322081813366742custom 53414855299238703381
[инст] #jimin pt.2 — 🫠
custom 534148552992387033860custom 535528111090749390118custom 534133220818133667412custom 52490951097351031544custom 52626490601536342683
🥹🥹🥹🥹🥹🥹🥹🥹🥹
custom 5355281110907493901139custom 526264906015363426855custom 534148552992387033834custom 52490951097351031542
[инст] #taehyung как красиво и мило 😭
custom 5355281110907493901102custom 524909510973510315431custom 534148552992387033820custom 52626490601536342685custom 53413322081813366741
не все отменяйте тур хватит доигрались
custom 5269494168576603603152custom 534133220818133667438custom 534144235691261013724custom 52626490601536342687custom 53414855299238703382custom 52490951097351031541custom 53552811109074939011
умираю его лицо 😭😭
custom 524909510973510315497custom 535528111090749390125custom 534144235691261013715custom 52626490601536342688custom 53413322081813366741custom 53414855299238703381
ОНИ. ВЫСТУПИЛИ. С. PARADISE. FUUUUCK
custom 534148552992387033897custom 526949416857660360339custom 535528111090749390124custom 52490951097351031548custom 52626490601536342685custom 53369930241970115611custom 53413322081813366741
[инст] #jin как всегда хорош
custom 535528111090749390191custom 534148552992387033826custom 534133220818133667420custom 52626490601536342684
Showing the 9 most recent of 9 posts we hold for @ipgb_taekook. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ipgb: you are my safe place” (@ipgb_taekook), 3,276 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ipgb_taekook.
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.