BIZTRAC BETA
Buying and selling of own real estate

GAMLE DALAVEGEN 88 AS

Org. no. 912979652 Limited company (AS) Kvam Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 935,000
Equity NOK 3.0m
Incorporated 2013
Share capital NOK 37,000

GAMLE DALAVEGEN 88 AS is registered as a limited company in Kvam, Vestland with organisation number 912979652. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 37,000, divided into 1000 shares. The company's stated purpose is: “Drive økonomisk virksomhet av enhver art, men med hovedvekt på å eie aksjer og andeler i andre selskaper og kjøp/salg av fast eiendom, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 935,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 935,000
Equity
NOK 3.0m
Est. value
NOK 4.0m

Financial health · 2024

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.1%
Very good
Equity as a share of total capital

Who owns GAMLE DALAVEGEN 88 AS?

ODDVAR BJARTE VANGDAL
GAMLE DALAVEGEN 88 AS
NOK 1.6m rev. · NOK 935,000 profit

GAMLE DALAVEGEN 88 AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GAMLE DALAVEGEN 88 AS

Who owns GAMLE DALAVEGEN 88 AS?

ODDVAR BJARTE VANGDAL is the largest registered owner, with 27.5%.

What is the revenue of GAMLE DALAVEGEN 88 AS?

GAMLE DALAVEGEN 88 AS had revenue of NOK 1.6m in 2024.

Who is the general manager of GAMLE DALAVEGEN 88 AS?

Oddvar Bjarte Vangdal is registered as general manager of GAMLE DALAVEGEN 88 AS.

Where is GAMLE DALAVEGEN 88 AS based?

GAMLE DALAVEGEN 88 AS has its business address in Norheimsund.

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.