biztrac. BETA
COMPANY REGISTER PROFILE
987921439 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Civil engineering activities

AKER PROSJEKT AS

Org. no. 987921439 Limited company (AS) Asker Incorporated 2005 Active
Revenue 2025 NOK 24,000
Operating profit NOK −56,000
Equity NOK 248,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

AKER PROSJEKT AS is registered as a limited company in Asker, Akershus with organisation number 987921439. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Tilby tjenester innen utvikling og ledelse av eiendomsprosjekter samt byggeledelse og realisering. Både bolig, næringseiendom samt annen fast eiendom og hermed beslektede områder.”. The most recent filed accounts, for the 2025 financial year, show NOK 24,000 in revenue and NOK −56,000 in operating profit.

Key figures · 2025

Revenue
NOK 24,000
▼ −14 %
Operating profit
NOK −56,000
▼ −8 %
Equity
NOK 248,000
▼ −18 %
Est. value
NOK 146,000

Financial health · 2025

Liquidity
4.59
Very good
Current assets ÷ current liabilities
Profitability
-13.8%
Not satisfactory
Return on total assets
Solidity
78.2%
Very good
Equity as a share of total capital

Who owns AKER PROSJEKT AS?

AKER PROSJEKT AS
NOK 24,000 rev. · NOK −56,000 profit

AKER PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AKER PROSJEKT AS

Who owns AKER PROSJEKT AS?

Atle Reidulff is the largest registered owner, with 100.0%.

What is the revenue of AKER PROSJEKT AS?

AKER PROSJEKT AS had revenue of NOK 24,000 in 2025.

Where is AKER PROSJEKT AS based?

AKER PROSJEKT AS has its business address in Hvalstad.

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.