BIZTRAC BETA
Rental and operating of own or leased real estate

VESTRE RINGVEI 5 AS

Org. no. 995372959 Limited company (AS) Indre Østfold Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 822,000
Operating profit NOK 633,000
Equity NOK 803,000
Incorporated 2010
Share capital NOK 1.0m

VESTRE RINGVEI 5 AS is registered as a limited company in Indre Østfold, Østfold with organisation number 995372959. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Eiendomsvirksomhet samt hva dermed står i forbindelse, herunder deltagelse i andre selskaper, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 822,000 in revenue and NOK 633,000 in operating profit.

Key figures · 2025

Revenue
NOK 822,000
Operating profit
NOK 633,000
Equity
NOK 803,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns VESTRE RINGVEI 5 AS?

FITLAND AS
VESTRE RINGVEI 5 AS
NOK 822,000 rev. · NOK 633,000 profit

VESTRE RINGVEI 5 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTRE RINGVEI 5 AS

Who owns VESTRE RINGVEI 5 AS?

FITLAND AS is the largest registered owner, with 100.0%.

What is the revenue of VESTRE RINGVEI 5 AS?

VESTRE RINGVEI 5 AS had revenue of NOK 822,000 in 2025.

Who is the general manager of VESTRE RINGVEI 5 AS?

Stein Dag Tønjum is registered as general manager of VESTRE RINGVEI 5 AS.

Where is VESTRE RINGVEI 5 AS based?

VESTRE RINGVEI 5 AS has its business address in Askim.

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.