BIZTRAC BETA
Rental and operating of own or leased real estate

VESTERDALSVEGEN 811 AS

Org. no. 832206172 Limited company (AS) Kvinesdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 99,000
Operating profit NOK 54,000
Equity NOK 338,000
Incorporated 2023
Share capital NOK 200,000

VESTERDALSVEGEN 811 AS is registered as a limited company in Kvinesdal, Agder with organisation number 832206172. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Investering i verdipapir, fast eiendom, og alt hva dermed står i forbindelse, samt deltagelse i andre virksomheter av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 99,000 in revenue and NOK 54,000 in operating profit.

Key figures · 2024

Revenue
NOK 99,000
Operating profit
NOK 54,000
Equity
NOK 338,000
Est. value
NOK 312,000

Financial health · 2024

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.9%
Good
Equity as a share of total capital

Who owns VESTERDALSVEGEN 811 AS?

OKSEFJELL INVEST AS
VESTERDALSVEGEN 811 AS
NOK 99,000 rev. · NOK 54,000 profit

VESTERDALSVEGEN 811 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VESTERDALSVEGEN 811 AS

Who owns VESTERDALSVEGEN 811 AS?

OKSEFJELL INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of VESTERDALSVEGEN 811 AS?

VESTERDALSVEGEN 811 AS had revenue of NOK 99,000 in 2024.

Who is the general manager of VESTERDALSVEGEN 811 AS?

Øystein Røynestad is registered as general manager of VESTERDALSVEGEN 811 AS.

Where is VESTERDALSVEGEN 811 AS based?

VESTERDALSVEGEN 811 AS has its business address in Kvinesdal.

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.