BIZTRAC BETA
Other mining and quarrying n.e.c.

GUDVANGEN STEIN DRIFT AS

Org. no. 929720431 Limited company (AS) Aurland Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 14.2m
Operating profit NOK 4.8m
Equity NOK 22.7m
Incorporated 2022
Employees 25
Share capital NOK 1.2m

GUDVANGEN STEIN DRIFT AS is registered as a limited company in Aurland, Vestland with organisation number 929720431. The business is classified under other mining and quarrying n.e.c. (NACE 08.990). The company was incorporated in 2022 and has 25 registered employees. Registered share capital is NOK 1.2m, divided into 3000 shares. The company's stated purpose is: “Utvinning av anortositt (kvitstein) og bearbeiding av denne, samt annen virksomhet som har tilknytting til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.2m in revenue and NOK 4.8m in operating profit.

Key figures · 2024

Revenue
NOK 14.2m
Operating profit
NOK 4.8m
Equity
NOK 22.7m
Est. value
NOK 23.4m

Financial health · 2024

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

Who owns GUDVANGEN STEIN DRIFT AS?

Gudvangen Stein AS
GUDVANGEN STEIN DRIFT AS
NOK 14.2m rev. · NOK 4.8m profit

GUDVANGEN STEIN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GUDVANGEN STEIN DRIFT AS

Who owns GUDVANGEN STEIN DRIFT AS?

Gudvangen Stein AS is the largest registered owner, with 100.0%.

What is the revenue of GUDVANGEN STEIN DRIFT AS?

GUDVANGEN STEIN DRIFT AS had revenue of NOK 14.2m in 2024.

Who is the general manager of GUDVANGEN STEIN DRIFT AS?

Frode Øvsthus is registered as general manager of GUDVANGEN STEIN DRIFT AS.

Where is GUDVANGEN STEIN DRIFT AS based?

GUDVANGEN STEIN DRIFT AS has its business address in Gudvangen.

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.