BIZTRAC BETA
Intermediation service activities for real estate activities

STORHAUG + PARTNERE AS

Org. no. 931694022 Limited company (AS) Tromsø Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 12.2m
Operating profit NOK 994,000
Equity NOK 424,000
Incorporated 2023
Share capital NOK 420,000

STORHAUG + PARTNERE AS is registered as a limited company in Tromsø, Troms with organisation number 931694022. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2023. Registered share capital is NOK 420,000, divided into 3000 shares. The company's stated purpose is: “Drive eiendomsmegling av både nye og brukte eiendommer, samt det som naturlig står i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.2m in revenue and NOK 994,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.2m
Operating profit
NOK 994,000
Equity
NOK 424,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns STORHAUG + PARTNERE AS?

ARCEO HOLDING AS
STORHAUG + PARTNERE AS
NOK 12.2m rev. · NOK 994,000 profit

STORHAUG + PARTNERE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORHAUG + PARTNERE AS

Who owns STORHAUG + PARTNERE AS?

ARCEO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STORHAUG + PARTNERE AS?

STORHAUG + PARTNERE AS had revenue of NOK 12.2m in 2025.

Who is the general manager of STORHAUG + PARTNERE AS?

Einar Nyland-Storhaug is registered as general manager of STORHAUG + PARTNERE AS.

Where is STORHAUG + PARTNERE AS based?

STORHAUG + PARTNERE AS has its business address in Tromsø.

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.