Telegram RegisterThe public register of Telegram

Channel

Kombat Protocol

@KombatProtocol

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

20subscribers

+0 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-1001617898779
TypeChannel
Username@KombatProtocol
DescriptionAutostaking and autocompounding Protocol with a Mobile game live on app stores
CreatedBetween 1 December 2021 and 4 April 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/KombatProtocol

Growth

207 August 2026 — 20 subscribers11 August 2026 — 20 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 19–21 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 15:4620no change
7 Aug 2026, 05:1420first reading

Engagement

20 posts held, back to 4 April 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 8 April 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
10
Videos
2
Links
25

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

8 Apr 2022, 20:05 UTC315 viewsread 11 August 2026

We are live Dextools Chart link: https://www.dextools.io/app/bsc/pair-explorer/0xfb00f177ee2fbe6ac3da71e4a686d496df5dfd78 Pancakeswap link: https://pancakeswap.finance/swap?inputCurrency=0x05d0178435adab55b7d37d155f29d615ea6df202

8 Apr 2022, 19:06 UTC308 viewsread 11 August 2026

We are not yet live We will inform you once we are live for trading

8 Apr 2022, 17:44 UTC247 viewsread 11 August 2026

Listing on Pancakeswap will be delayed to help get Cg and Cmc listing plan Please bear with us

8 Apr 2022, 17:16 UTC235 viewsread 11 August 2026

Fairlaunch has ended 61bnb raised with 131 contributors You can claim on pinksale on listing

8 Apr 2022, 13:44 UTC269 viewsread 11 August 2026

Last chance to contribute Fairlaunch ends in 3 hours https://www.pinksale.finance/#/launchpad/0xBDA3986544DD3b12A0B64e0ba5b4D208393Ab0eA?chain=BSC Top contributors get legend NFT and earn highest bnb rewards

5 Apr 2022, 21:14 UTC425 viewsread 11 August 2026
Photo

Unveiling Kombat Protocol NFTs 🔥 NFT AIRDROP FOR FAIR LAUNCH CONTRIBUTORS 🔥 💥 Together, we give you free NFTs with a total of up to 500NFTs for the TOP CONTRIBUTORS in Fair Launch! 🎁 Rewards: Top 1-10: 1 Random NFT legend Top 11-50: 1 Random NFT Epic Top 51-200: 1 Random NFT Rare Other contributors: 1 Random NFT Common (Min contribute 0.1 BNB for being eligible - Max 300 Common NFTs will be airdropped. If ther

5 Apr 2022, 16:27 UTC361 viewsread 11 August 2026

https://twitter.com/kombatprotocol/status/1511379412687769605?s=21 iOS Beta version is up guys Retweet let's spread the word

5 Apr 2022, 16:21 UTC363 viewsread 11 August 2026

Brazilian channel supporting us https://youtu.be/jP9K9vpHM8o

5 Apr 2022, 15:53 UTC314 viewsread 11 August 2026

Cointiger Listing immediately after launch Get ready to moon 🚀🚀🚀

Showing the 12 most recent of 20 posts we hold for @KombatProtocol. 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.

Mentions

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Kombat Protocol” (@KombatProtocol), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/KombatProtocol.

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.