BIZTRAC BETA
Architectural activities

ARKHAUS AS

Org. no. 913014499 Limited company (AS) Hammerfest Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 23,000
Operating profit NOK −86,000
Equity NOK −485,000
Incorporated 2013
Share capital NOK 130,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−485k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−86k kr).

ARKHAUS AS is registered as a limited company in Hammerfest, Finnmark with organisation number 913014499. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2013. Registered share capital is NOK 130,000, divided into 130 shares. The company's stated purpose is: “Å drive eit arkitektkontor som skal levere alle teneste innanfor arkitekturen inkl. landskapsarkitektur og illustrasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 23,000 in revenue and NOK −86,000 in operating profit.

Key figures · 2025

Revenue
NOK 23,000
Operating profit
NOK −86,000
Equity
NOK −485,000

Financial health · 2025

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

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

Who owns ARKHAUS AS?

ALEXANDER KUPZ
ARKHAUS AS
NOK 23,000 rev. · NOK −86,000 profit

ARKHAUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARKHAUS AS

Who owns ARKHAUS AS?

ALEXANDER KUPZ is the largest registered owner, with 100.0%.

What is the revenue of ARKHAUS AS?

ARKHAUS AS had revenue of NOK 23,000 in 2025.

Who is the general manager of ARKHAUS AS?

Alexander Kupz is registered as general manager of ARKHAUS AS.

Where is ARKHAUS AS based?

ARKHAUS AS has its business address in Hammerfest.

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.