Channel
@kissepubg
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
361subscribers
-140 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002369147703 |
|---|---|
| Type | Channel |
| Username | @kissepubg |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/kissepubg |
Gaming — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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 |
|---|---|---|
| 17 Sept 2026, 12:58 | 361 | -89 |
| 9 Sept 2026, 23:40 | 450 | -30 |
| 31 Aug 2026, 18:34 | 480 | -8 |
| 24 Aug 2026, 06:15 | 488 | -3 |
| 16 Aug 2026, 22:05 | 491 | -10 |
| 9 Aug 2026, 20:53 | 501 | no change |
| 9 Aug 2026, 02:31 | 501 | first reading |
19 posts held, back to 15 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 19 posts for this entry, the most recent from 6 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.
80 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 37.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5292160596488243041 | 30 | 37.5% | |
| custom 5420402706424564042 | 25 | 31.3% | |
| custom 5300974762732826916 | 10 | 12.5% | |
| 🔥 | 6 | 7.50% | |
| custom 5325799179782471162 | 5 | 6.25% | |
| custom 5422682247432010020 | 2 | 2.50% | |
| 💋 | 2 | 2.50% |
Custom emoji. 5 of the rows above are 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 11 of the 19 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 80 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 15 July 2026 to 6 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.
🔗нет так нет вы проебали низкие цены которые ниже ринка (но он меняется) пример 2300uc+подарок 2200₽ 4500uc+подарок 4250₽ ( подарок это доп юс) Ебала стараться и делать что-то если это никто не ценит 🔗Розыгрыши и возможно турниры будут а так с шопом бб
custom 54204027064245640422custom 53009747627328269161
Posted without readable text
«Смешно наблюдать, как человек, который сам бегает по каждому МОЕМУ розыгрышу и пытается урвать любой приз, потом строит из себя эксперта и пытается кого-то задеть. Со стороны это выглядит не как уверенность, а как обычная попытка привлечь внимание свинота ебаная. Такое ощущение, что мой профиль тебя интересует больше, чем собственная жизнь. Продолжай следить, комментировать и обсуждать — бесплатный актив ещё никому …
custom 53009747627328269164🔥2custom 52921605964882430412custom 54204027064245640421
Ладно и так идеально 🤍🐾
custom 52921605964882430412custom 53257991797824711621custom 54204027064245640421
Покупаем мне каблуки бегом 🦇
custom 52921605964882430412🔥1custom 53257991797824711621
Video message, posted without a caption
Результаты конкурса: 🥳 Победители: 1. Tomas (@Focfy) 2. ES¹LiZynChlk (@lovik324) 3. - 4. nnn (@heavikxxl) Проверить результаты ✅
custom 52921605964882430412
Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]
Кто участвует ставим реакции 🤍
custom 52921605964882430419custom 54204027064245640424💋1
Розыгрыш закончился 🖤
custom 529216059648824304110custom 54204027064245640428custom 53009747627328269164💋1
Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]
Малой отлетел 🔞
🔅запускаем стрим с вепкой вечером?🔅 и в тдм летим
custom 54204027064245640424custom 52921605964882430412custom 53009747627328269161
Докиньте мне люто юс 51632375367 🖤
custom 52921605964882430411
Showing the 12 most recent of 19 posts we hold for @kissepubg. 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.
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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“KISSE” (@kissepubg), 361 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/kissepubg.
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.