BIZTRAC BETA
Rental and operating of own or leased real estate

VÅLERVEIEN 49 AS

Org. no. 919797150 Limited company (AS) Moss Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 542,000
Operating profit NOK −200,000
Equity NOK 87,000
Incorporated 2017
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−200k kr).

VÅLERVEIEN 49 AS is registered as a limited company in Moss, Østfold with organisation number 919797150. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Ervervelse, utbygging, forvaltning og utleie av fast eiendom, investering i aksjer og andre verdipapirer herunder å investere i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 542,000 in revenue and NOK −200,000 in operating profit.

Key figures · 2024

Revenue
NOK 542,000
Operating profit
NOK −200,000
Equity
NOK 87,000
Est. value
NOK 505,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VÅLERVEIEN 49 AS?

OMSTILLING AS
VÅLERVEIEN 49 AS
NOK 542,000 rev. · NOK −200,000 profit

VÅLERVEIEN 49 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VÅLERVEIEN 49 AS

Who owns VÅLERVEIEN 49 AS?

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

What is the revenue of VÅLERVEIEN 49 AS?

VÅLERVEIEN 49 AS had revenue of NOK 542,000 in 2024.

Where is VÅLERVEIEN 49 AS based?

VÅLERVEIEN 49 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.