BIZTRAC BETA
COMPANY REGISTER PROFILE
934186133 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Architectural activities

HAAK ARKITEKTUR & DESIGN AS

Org. no. 934186133 Limited company (AS) Nannestad Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 22,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

HAAK ARKITEKTUR & DESIGN AS is registered as a limited company in Nannestad, Akershus with organisation number 934186133. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen arkitektur og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2024

Operating profit
NOK −3,000
Equity
NOK 22,000
Est. value
NOK 36,000

Financial health · 2024

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

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

Who owns HAAK ARKITEKTUR & DESIGN AS?

SUSANN HÅKENSTAD
HAAK ARKITEKTUR & DESIGN AS
· NOK −3,000 profit

HAAK ARKITEKTUR & DESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAAK ARKITEKTUR & DESIGN AS

Who owns HAAK ARKITEKTUR & DESIGN AS?

SUSANN HÅKENSTAD is the largest registered owner, with 100.0%.

Who is the general manager of HAAK ARKITEKTUR & DESIGN AS?

Susann Håkenstad is registered as general manager of HAAK ARKITEKTUR & DESIGN AS.

Where is HAAK ARKITEKTUR & DESIGN AS based?

HAAK ARKITEKTUR & DESIGN AS has its business address in Holter.

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.