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

VOLDA ØRSTA FLYKLUBB EIGEDOM AS

Org. no. 917823936 Limited company (AS) Ørsta Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 467,000
Operating profit NOK 266,000
Equity NOK 1.0m
Incorporated 2016
Share capital NOK 250,000

VOLDA ØRSTA FLYKLUBB EIGEDOM AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 917823936. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 250,000, divided into 1000 shares. The company's stated purpose is: “Eige og drive utleige av garasje og flyhangar.”. The most recent filed accounts, for the 2025 financial year, show NOK 467,000 in revenue and NOK 266,000 in operating profit.

Key figures · 2025

Revenue
NOK 467,000
▲ +18 %
Operating profit
NOK 266,000
▲ +38 %
Equity
NOK 1.0m
▲ +7 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
7.4%
Satisfactory
Return on total assets
Solidity
29.0%
Good
Equity as a share of total capital

Who owns VOLDA ØRSTA FLYKLUBB EIGEDOM AS?

VOLDA ØRSTA FLYKLUBB EIGEDOM AS
NOK 467,000 rev. · NOK 266,000 profit

VOLDA ØRSTA FLYKLUBB EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOLDA ØRSTA FLYKLUBB EIGEDOM AS

Who owns VOLDA ØRSTA FLYKLUBB EIGEDOM AS?

VOLDA ØRSTA FLYKLUBB is the largest registered owner, with 100.0%.

What is the revenue of VOLDA ØRSTA FLYKLUBB EIGEDOM AS?

VOLDA ØRSTA FLYKLUBB EIGEDOM AS had revenue of NOK 467,000 in 2025.

Where is VOLDA ØRSTA FLYKLUBB EIGEDOM AS based?

VOLDA ØRSTA FLYKLUBB EIGEDOM AS has its business address in Hovdebygda.

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.