BIZTRAC BETA
Buying and selling of own real estate

MOTHERSHIP AS

Org. no. 892114692 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.2m
Equity NOK 1.8m
Incorporated 2007
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

MOTHERSHIP AS is registered as a limited company in Oslo, Oslo with organisation number 892114692. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2007. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, kjøp, salg og drift av fast eiendom. Samt hva som herav naturlig står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.2m
Equity
NOK 1.8m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns MOTHERSHIP AS?

ESPEN SKAAR
MOTHERSHIP AS
NOK 0 rev. · NOK −1.2m profit

MOTHERSHIP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MOTHERSHIP AS own?

MOTHERSHIP AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about MOTHERSHIP AS

Who owns MOTHERSHIP AS?

ESPEN SKAAR is the largest registered owner, with 100.0%.

What is the revenue of MOTHERSHIP AS?

MOTHERSHIP AS had revenue of NOK 0 in 2024.

Who is the general manager of MOTHERSHIP AS?

Espen Skaar is registered as general manager of MOTHERSHIP AS.

Where is MOTHERSHIP AS based?

MOTHERSHIP 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.