BIZTRAC BETA
COMPANY REGISTER PROFILE
922149313 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

KATRINE SOLBAKKE AS

Org. no. 922149313 Limited company (AS) Lillestrøm Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −623,000
Equity NOK 15.6m
Incorporated 2018
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−623k kr).

KATRINE SOLBAKKE AS is registered as a limited company in Lillestrøm, Akershus with organisation number 922149313. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 50 shares. The company's stated purpose is: “Å ha aksjer i andre selskaper, samt virksomhet med tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −623,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −623,000
Equity
NOK 15.6m
Est. value
NOK 18.3m

Financial health · 2025

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

Who owns KATRINE SOLBAKKE AS?

KATRINE SOLBAKKE
KATRINE SOLBAKKE AS
NOK 0 rev. · NOK −623,000 profit

KATRINE SOLBAKKE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KATRINE SOLBAKKE AS own?

KATRINE SOLBAKKE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KATRINE SOLBAKKE AS

Who owns KATRINE SOLBAKKE AS?

KATRINE SOLBAKKE is the largest registered owner, with 100.0%.

What is the revenue of KATRINE SOLBAKKE AS?

KATRINE SOLBAKKE AS had revenue of NOK 0 in 2025.

Where is KATRINE SOLBAKKE AS based?

KATRINE SOLBAKKE AS has its business address in Strømmen.

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.