BIZTRAC BETA
Rental and operating of own or leased real estate

STADIONVEGEN AS

Org. no. 993254142 Limited company (AS) Kvinesdal Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK −508,000
Equity NOK 1.4m
Incorporated 2008
Share capital NOK 3.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−508k kr).

STADIONVEGEN AS is registered as a limited company in Kvinesdal, Agder with organisation number 993254142. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 3.0m, divided into 1000 shares. The company's stated purpose is: “Eie, utvikle og leie ut fast eiendom, etablere handels- og servicevirksomhet, invester i andre selskaper, og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −508,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK −508,000
Equity
NOK 1.4m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns STADIONVEGEN AS?

OKR HOLDING AS
STADIONVEGEN AS
NOK 2.4m rev. · NOK −508,000 profit

STADIONVEGEN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about STADIONVEGEN AS

Who owns STADIONVEGEN AS?

OKR HOLDING AS is the largest registered owner, with 31.0%.

What is the revenue of STADIONVEGEN AS?

STADIONVEGEN AS had revenue of NOK 2.4m in 2025.

Who is the general manager of STADIONVEGEN AS?

Per Erik Røgenes is registered as general manager of STADIONVEGEN AS.

Where is STADIONVEGEN AS based?

STADIONVEGEN 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.