BIZTRAC BETA
Rental and operating of own or leased real estate

VITAMINVEIEN 28 AS

Org. no. 833909312 Limited company (AS) Lørenskog Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 513,000
Operating profit NOK 472,000
Equity NOK 2.9m
Incorporated 2024
Share capital NOK 30,000

Signals

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

VITAMINVEIEN 28 AS is registered as a limited company in Lørenskog, Akershus with organisation number 833909312. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å investere i fast eiendom, herunder å eie aksjer, obligasjoner, andeler i selskap etter selskapsloven og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 513,000 in revenue and NOK 472,000 in operating profit.

Key figures · 2024

Revenue
NOK 513,000
Operating profit
NOK 472,000
Equity
NOK 2.9m
Est. value
NOK 3.1m

Financial health · 2024

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.3%
Very good
Equity as a share of total capital

Who owns VITAMINVEIEN 28 AS?

VH EIENDOM AS
VITAMINVEIEN 28 AS
NOK 513,000 rev. · NOK 472,000 profit

VITAMINVEIEN 28 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VITAMINVEIEN 28 AS

Who owns VITAMINVEIEN 28 AS?

VH EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of VITAMINVEIEN 28 AS?

VITAMINVEIEN 28 AS had revenue of NOK 513,000 in 2024.

Where is VITAMINVEIEN 28 AS based?

VITAMINVEIEN 28 AS has its business address in Fjellhamar.

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.