Telegram RegisterThe public register of Telegram
Telegram profile photo for Hamster Kombat

Channel

Hamster Kombat

@Hamster_Kombatkoin

On this record: Growth · Engagement · Posts · Citations · Cite this entry

40subscribers

+1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002244951465
TypeChannel
Username@Hamster_Kombatkoin
CreatedBetween 1 May 2024 and 28 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/Hamster_Kombatkoin

Growth

394039.56 August 2026 — 39 subscribers10 August 2026 — 39 subscribers18 September 2026 — 40 subscribers6 August 202618 September 2026
3 measurements spanning 43 days, net +1. 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 39–40 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 09:3640+1
10 Aug 2026, 19:4639no change
6 Aug 2026, 17:4939first reading

Engagement

20 posts held, back to 28 September 2024the 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 28 September 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

28 Sept 2024, 22:56 UTC7 viewsread 10 August 2026

https://t.me/OKX_official_bot/OKX_Racer?startapp=linkCode_125007222 Let's race! Predict Bitcoin's price and rack up points

28 Sept 2024, 22:56 UTC15 viewsread 10 August 2026

https://t.me/money_dogs_bot/money_dogs?startapp=N1MsgYLe Who let the Money Dogs out?

28 Sept 2024, 22:56 UTC16 viewsread 10 August 2026

💎 Claim 500 free $MOLE ⛏ Let's see who digs deeper: https://t.me/TonMole_Bot/game?startapp=ref_5967592084

28 Sept 2024, 22:56 UTC36 viewsread 10 August 2026

https://t.me/metaracinggame_bot/app?startapp=bonus_bddiidoick Let's race-to-earn right now!

28 Sept 2024, 22:56 UTC6 viewsread 10 August 2026

https://t.me/booms_io_bot/start?startapp=bro5967592084 BOOMS Game - Earn tokens with real value even before the airdrop! Take your welcome bonus: 💸 50000 Coins as a first-time gift 🔥 250000 Coins if you have Telegram Premium

28 Sept 2024, 22:56 UTC40 viewsread 10 August 2026

https://t.me/Racememe_bot?start=r_5967592084 🏎 Play in $RACE to Billion with me and earn a share of an airdrop of the most anticipated meme on Solana

28 Sept 2024, 22:56 UTC41 viewsread 10 August 2026

https://t.me/pixelversexyzbot?start=5967592084 Let's fight for rewards together! Take your welcome bonus: 💸 2,000 Coins 2X multiplier for the first 24 hours 🔥 10,000 Coins 3X multiplier if you have Telegram Premium

28 Sept 2024, 22:56 UTC7 viewsread 10 August 2026

t.me/hrummebot/game?startapp=ref5967592084 من به تو یک شیرینی شانس می‌دهم

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

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.

Mentions

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.

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

“Hamster Kombat” (@Hamster_Kombatkoin), 40 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Hamster_Kombatkoin.

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.