biztrac. BETA
COMPANY REGISTER PROFILE
923154442 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SALTLAGERET KAIDRIFT AS

Org. no. 923154442 Limited company (AS) Ålesund Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 54,000
Equity NOK 896,000
Incorporated 2019
Share capital NOK 200,000

SALTLAGERET KAIDRIFT AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 923154442. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Utleie av kaianlegg og relatert virksomhet, herunder å delta i selskap og virksomheter med beslektet virksomhet, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 54,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▼ −6 %
Operating profit
NOK 54,000
▼ −3 %
Equity
NOK 896,000
▲ +5 %
Est. value
NOK 782,000

Financial health · 2025

Liquidity
6.39
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
84.4%
Very good
Equity as a share of total capital

Who owns SALTLAGERET KAIDRIFT AS?

SALTLAGERET KAIDRIFT AS
NOK 1.5m rev. · NOK 54,000 profit

SALTLAGERET KAIDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SALTLAGERET KAIDRIFT AS

Who owns SALTLAGERET KAIDRIFT AS?

Ola Volstad is the largest registered owner, with 50.0%.

What is the revenue of SALTLAGERET KAIDRIFT AS?

SALTLAGERET KAIDRIFT AS had revenue of NOK 1.5m in 2025.

Where is SALTLAGERET KAIDRIFT AS based?

SALTLAGERET KAIDRIFT AS has its business address in Ålesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.