BIZTRAC BETA
Uoppgitt

KSKB HOLDING AS

Org. no. 936178731 Limited company (AS) Lillestrøm Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −167
Equity NOK 33,000
Incorporated 2025
Share capital NOK 40,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−167 kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-02.

KSKB HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 936178731. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −167
Equity
NOK 33,000
Est. value
NOK 39,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KSKB HOLDING AS?

KSUND HOLDING AS
KSKB HOLDING AS
· NOK −167 profit

KSKB HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KSKB HOLDING AS own?

KSKB HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KSKB HOLDING AS

Who owns KSKB HOLDING AS?

KSUND HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of KSKB HOLDING AS?

Kristian Johnsen Blomhoff is registered as general manager of KSKB HOLDING AS.

Where is KSKB HOLDING AS based?

KSKB HOLDING AS has its business address in Lillestrøm.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.