BIZTRAC BETA
Rental and operating of own or leased real estate

VANEMVEIEN 19 AS

Org. no. 926756303 Limited company (AS) Ringsaker Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 590,000
Equity NOK 5.9m
Incorporated 2021
Share capital NOK 2.0m

Signals

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

VANEMVEIEN 19 AS is registered as a limited company in Ringsaker, Innlandet with organisation number 926756303. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 2.0m, divided into 1000 shares. The company's stated purpose is: “Utvikling og forvaltning av fast eiendom, aksjer, verdipapirer og andre formuesverdier av hvilken som helst art, herunder utlån av selskapets verdier, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 590,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 590,000
Equity
NOK 5.9m
Est. value
NOK 5.0m

Financial health · 2024

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.5%
Good
Equity as a share of total capital

Who owns VANEMVEIEN 19 AS?

VA 365 EIENDOM AS
VANEMVEIEN 19 AS
NOK 1.5m rev. · NOK 590,000 profit

VANEMVEIEN 19 AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about VANEMVEIEN 19 AS

Who owns VANEMVEIEN 19 AS?

VA 365 EIENDOM AS is the largest registered owner, with 91.6%.

What is the revenue of VANEMVEIEN 19 AS?

VANEMVEIEN 19 AS had revenue of NOK 1.5m in 2024.

Where is VANEMVEIEN 19 AS based?

VANEMVEIEN 19 AS has its business address in Furnes.

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.