BIZTRAC BETA
Joinery installation

STORVANN MULTISERVICE AS

Org. no. 935097371 Limited company (AS) Alta Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 180,000
Equity NOK 160,000
Incorporated 2025
Share capital NOK 30,000

STORVANN MULTISERVICE AS is registered as a limited company in Alta, Finnmark with organisation number 935097371. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Ta oppdrag innenfor bygg og anleggsbransjen. Utleie av arbeidskraft. Oppdrag i transportbransjen. Og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 180,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 180,000
Equity
NOK 160,000
Est. value
NOK 574,000

Financial health · 2025

Liquidity
2.22
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.7%
Good
Equity as a share of total capital

Who owns STORVANN MULTISERVICE AS?

ØYVIND ROMSDAL STORVANN
STORVANN MULTISERVICE AS
NOK 1.2m rev. · NOK 180,000 profit

STORVANN MULTISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORVANN MULTISERVICE AS

Who owns STORVANN MULTISERVICE AS?

ØYVIND ROMSDAL STORVANN is the largest registered owner, with 100.0%.

What is the revenue of STORVANN MULTISERVICE AS?

STORVANN MULTISERVICE AS had revenue of NOK 1.2m in 2025.

Who is the general manager of STORVANN MULTISERVICE AS?

Øyvind Romsdal Storvann is registered as general manager of STORVANN MULTISERVICE AS.

Where is STORVANN MULTISERVICE AS based?

STORVANN MULTISERVICE AS has its business address in Tverrelvdalen.

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.