BIZTRAC BETA
Activities of excursion and event organisers

29-2 AURLAND AS

Org. no. 999577547 Limited company (AS) Aurland Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 18.5m
Operating profit NOK 1.3m
Equity NOK 3.4m
Incorporated 2012
Employees 17
Share capital NOK 30,000

29-2 AURLAND AS is registered as a limited company in Aurland, Vestland with organisation number 999577547. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2012 and has 17 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kurs- og turistnæring, samt utleie av fast eiendom, samt hva som naturlig hører med.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 18.5m
Operating profit
NOK 1.3m
Equity
NOK 3.4m
Est. value
NOK 7.5m

Financial health · 2025

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
57.6%
Very good
Equity as a share of total capital

Who owns 29-2 AURLAND AS?

TONE RØNNING VIKE
29-2 AURLAND AS
NOK 18.5m rev. · NOK 1.3m profit

29-2 AURLAND AS has 2 registered shareholders:

All shareholders and roles →

Which companies does 29-2 AURLAND AS own?

29-2 AURLAND AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about 29-2 AURLAND AS

Who owns 29-2 AURLAND AS?

TONE RØNNING VIKE is the largest registered owner, with 50.0%.

What is the revenue of 29-2 AURLAND AS?

29-2 AURLAND AS had revenue of NOK 18.5m in 2025.

Who is the general manager of 29-2 AURLAND AS?

Tone Rønning Vike is registered as general manager of 29-2 AURLAND AS.

Where is 29-2 AURLAND AS based?

29-2 AURLAND AS has its business address in Aurland.

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.