BIZTRAC BETA
Uoppgitt

MIRJAM KULSTAD HOLDING AS

Org. no. 924285117 Limited company (AS) Nittedal Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −5,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5k kr).

MIRJAM KULSTAD HOLDING AS is registered as a limited company in Nittedal, Akershus with organisation number 924285117. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i næringsvirksomhet, herunder aksjer, eiendeler og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −5,000

Financial health · 2025

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

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

Who owns MIRJAM KULSTAD HOLDING AS?

MIRJAM KULSTAD NÆSS
MIRJAM KULSTAD HOLDING AS
NOK 0 rev. · NOK 0 profit

MIRJAM KULSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MIRJAM KULSTAD HOLDING AS own?

MIRJAM KULSTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MIRJAM KULSTAD HOLDING AS

Who owns MIRJAM KULSTAD HOLDING AS?

MIRJAM KULSTAD NÆSS is the largest registered owner, with 100.0%.

What is the revenue of MIRJAM KULSTAD HOLDING AS?

MIRJAM KULSTAD HOLDING AS had revenue of NOK 0 in 2025.

Where is MIRJAM KULSTAD HOLDING AS based?

MIRJAM KULSTAD HOLDING AS has its business address in Slattum.

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.