biztrac. BETA
COMPANY REGISTER PROFILE
995107171 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

AKERSHAVE EIENDOM AS

Org. no. 995107171 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −421,000
Equity NOK 44.0m
Incorporated 2010
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−421k kr).
  • Nylig endring 2026-05-06 Aksjekapital registrert 2026-05-06.

AKERSHAVE EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 995107171. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 500,000, divided into 140 shares. The company's stated purpose is: “Eie og drive fast eiendom, samt virksomhet som står i en naturlig sammenheng med dette.”.

Former names: NORSK STANDARDSELSKAP 177 AS

Key figures · 2025

Operating profit
NOK −421,000
▼ −5 %
Equity
NOK 44.0m
▲ +298 %
Est. value
NOK 217.5m

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
30.8%
Very good
Return on total assets
Solidity
20.7%
Good
Equity as a share of total capital

Who owns AKERSHAVE EIENDOM AS?

AKERSHAVE EIENDOM AS
· NOK −421,000 profit

AKERSHAVE EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does AKERSHAVE EIENDOM AS own?

AKERSHAVE EIENDOM AS holds stakes in 5 companies:

See the full ownership structure →

Group structure

AKERSHAVE EIENDOM AS er morselskap for 3 datterselskaper:

Frequently asked questions about AKERSHAVE EIENDOM AS

Who owns AKERSHAVE EIENDOM AS?

BOAS AS is the largest registered owner, with 95.0%.

Where is AKERSHAVE EIENDOM AS based?

AKERSHAVE EIENDOM 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 03.10.2026.

Report a problem

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