BIZTRAC BETA
Rental and operating of own or leased real estate

VÅLERVEIEN 159 AS

Org. no. 991110712 Limited company (AS) Moss Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 13.9m
Operating profit NOK 5.1m
Equity NOK 26.6m
Incorporated 2007
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VÅLERVEIEN 159 AS is registered as a limited company in Moss, Østfold with organisation number 991110712. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 1.0m, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investeringsvirksomhet, eiendomsforvaltning, forretningsførsel og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.9m in revenue and NOK 5.1m in operating profit.

Key figures · 2024

Revenue
NOK 13.9m
Operating profit
NOK 5.1m
Equity
NOK 26.6m
Est. value
NOK 25.5m

Financial health · 2025

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

Who owns VÅLERVEIEN 159 AS?

SKOLT HOLDING AS
VÅLERVEIEN 159 AS
NOK 13.9m rev. · NOK 5.1m profit

VÅLERVEIEN 159 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VÅLERVEIEN 159 AS

Who owns VÅLERVEIEN 159 AS?

SKOLT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VÅLERVEIEN 159 AS?

VÅLERVEIEN 159 AS had revenue of NOK 13.9m in 2024.

Where is VÅLERVEIEN 159 AS based?

VÅLERVEIEN 159 AS has its business address in Moss.

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.