BIZTRAC BETA
Development of building projects

STORE ÅROS VEI 38 AS

Org. no. 928138550 Limited company (AS) Holmestrand Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −30,000
Equity NOK 4.9m
Incorporated 2021
Share capital NOK 5.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−30k kr).

STORE ÅROS VEI 38 AS is registered as a limited company in Holmestrand, Vestfold with organisation number 928138550. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 5.0m, divided into 5000 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp og salg av fast eiendom, samt andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK 4.9m
Est. value
NOK 4.5m

Financial health · 2024

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

Who owns STORE ÅROS VEI 38 AS?

AGECO EIENDOM AS
STORE ÅROS VEI 38 AS
NOK 0 rev. · NOK −30,000 profit

STORE ÅROS VEI 38 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORE ÅROS VEI 38 AS

Who owns STORE ÅROS VEI 38 AS?

AGECO EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of STORE ÅROS VEI 38 AS?

STORE ÅROS VEI 38 AS had revenue of NOK 0 in 2025.

Where is STORE ÅROS VEI 38 AS based?

STORE ÅROS VEI 38 AS has its business address in Hof.

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.