BIZTRAC BETA
Architectural activities

ARKITEKTPARTNER AS

Org. no. 966360283 Limited company (AS) Frogn Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 94,000
Operating profit NOK 21,000
Equity NOK −182,000
Incorporated 1993
Share capital NOK 100,000

Signals

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

ARKITEKTPARTNER AS is registered as a limited company in Frogn, Akershus with organisation number 966360283. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 1993. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg og utvikling av arkitektjenester og det som ligger opptil slike aktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 94,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2024

Revenue
NOK 94,000
Operating profit
NOK 21,000
Equity
NOK −182,000
Est. value
NOK 119,000

Financial health · 2024

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

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

Who owns ARKITEKTPARTNER AS?

ODD ERIK HELÅSEN
ARKITEKTPARTNER AS
NOK 94,000 rev. · NOK 21,000 profit

ARKITEKTPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARKITEKTPARTNER AS

Who owns ARKITEKTPARTNER AS?

ODD ERIK HELÅSEN is the largest registered owner, with 100.0%.

What is the revenue of ARKITEKTPARTNER AS?

ARKITEKTPARTNER AS had revenue of NOK 94,000 in 2024.

Who is the general manager of ARKITEKTPARTNER AS?

Odd Erik Helåsen is registered as general manager of ARKITEKTPARTNER AS.

Where is ARKITEKTPARTNER AS based?

ARKITEKTPARTNER AS has its business address in Drøbak.

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.