BIZTRAC BETA
Rental and leasing of recreational and sports goods

KAYAK BALESTRAND AS

Org. no. 933250962 Limited company (AS) Sogndal Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 271,000
Operating profit NOK 28,000
Equity NOK 186,000
Incorporated 2024
Share capital NOK 194,000

KAYAK BALESTRAND AS is registered as a limited company in Sogndal, Vestland with organisation number 933250962. The business is classified under rental and leasing of recreational and sports goods (NACE 77.210). The company was incorporated in 2024. Registered share capital is NOK 194,000, divided into 194 shares. The company's stated purpose is: “Drift og utleige av utstyr til fjordaktivitetar, samt tilhøyrande tenester og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 271,000 in revenue and NOK 28,000 in operating profit.

Key figures · 2025

Revenue
NOK 271,000
Operating profit
NOK 28,000
Equity
NOK 186,000
Est. value
NOK 219,000

Financial health · 2025

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

Who owns KAYAK BALESTRAND AS?

KURT OVE LIDAL
KAYAK BALESTRAND AS
NOK 271,000 rev. · NOK 28,000 profit

KAYAK BALESTRAND AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KAYAK BALESTRAND AS

Who owns KAYAK BALESTRAND AS?

KURT OVE LIDAL is the largest registered owner, with 50.0%.

What is the revenue of KAYAK BALESTRAND AS?

KAYAK BALESTRAND AS had revenue of NOK 271,000 in 2025.

Where is KAYAK BALESTRAND AS based?

KAYAK BALESTRAND AS has its business address in Balestrand.

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.