BIZTRAC BETA
Civil engineering activities

JAK ARKITEKT AS

Org. no. 880976982 Limited company (AS) Aure Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 596,000
Operating profit NOK 287,000
Equity NOK −253,000
Incorporated 1999
Share capital NOK 100,000

Signals

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

JAK ARKITEKT AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 880976982. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester innen bygg og anleggsbransjen, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 596,000 in revenue and NOK 287,000 in operating profit.

Key figures · 2024

Revenue
NOK 596,000
Operating profit
NOK 287,000
Equity
NOK −253,000
Est. value
NOK 1.2m

Financial health · 2024

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

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

Who owns JAK ARKITEKT AS?

JAN ARVE KVISVIK
JAK ARKITEKT AS
NOK 596,000 rev. · NOK 287,000 profit

JAK ARKITEKT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JAK ARKITEKT AS

Who owns JAK ARKITEKT AS?

JAN ARVE KVISVIK is the largest registered owner, with 65.0%.

What is the revenue of JAK ARKITEKT AS?

JAK ARKITEKT AS had revenue of NOK 596,000 in 2024.

Who is the general manager of JAK ARKITEKT AS?

Jan Arve Kvisvik is registered as general manager of JAK ARKITEKT AS.

Where is JAK ARKITEKT AS based?

JAK ARKITEKT AS has its business address in Aure.

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.