BIZTRAC BETA
Other content distribution activities

SIMPLY HOLDING AS

Org. no. 931723510 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 67,000
Incorporated 2023
Share capital NOK 80,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

SIMPLY HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 931723510. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2023. Registered share capital is NOK 80,000, divided into 8000 shares. The company's stated purpose is: “Kapitalforvaltning.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 67,000
Est. value
NOK 122,000

Financial health · 2024

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

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

Who owns SIMPLY HOLDING AS?

THOR ØYVIND HAUGEN
SIMPLY HOLDING AS
NOK 0 rev. · NOK −7,000 profit

SIMPLY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIMPLY HOLDING AS own?

SIMPLY HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

SIMPLY HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about SIMPLY HOLDING AS

Who owns SIMPLY HOLDING AS?

THOR ØYVIND HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of SIMPLY HOLDING AS?

SIMPLY HOLDING AS had revenue of NOK 0 in 2024.

Where is SIMPLY HOLDING AS based?

SIMPLY HOLDING AS has its business address in Oslo.

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.