BIZTRAC BETA
Rental and operating of own or leased real estate

STOREVARVEIEN 390 AS

Org. no. 928337332 Limited company (AS) Sandefjord Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 506,000
Operating profit NOK 274,000
Equity NOK 341,000
Incorporated 2021
Share capital NOK 100,000

STOREVARVEIEN 390 AS is registered as a limited company in Sandefjord, Vestfold with organisation number 928337332. 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 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom med tilhørende tjenester og produkter. Selskapet skal også kunne investere i aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 506,000 in revenue and NOK 274,000 in operating profit.

Key figures · 2025

Revenue
NOK 506,000
Operating profit
NOK 274,000
Equity
NOK 341,000
Est. value
NOK 496,000

Financial health · 2025

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

Who owns STOREVARVEIEN 390 AS?

MYBIT HOLDING AS
STOREVARVEIEN 390 AS
NOK 506,000 rev. · NOK 274,000 profit

STOREVARVEIEN 390 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about STOREVARVEIEN 390 AS

Who owns STOREVARVEIEN 390 AS?

MYBIT HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of STOREVARVEIEN 390 AS?

STOREVARVEIEN 390 AS had revenue of NOK 506,000 in 2025.

Who is the general manager of STOREVARVEIEN 390 AS?

Åsmund Myhre is registered as general manager of STOREVARVEIEN 390 AS.

Where is STOREVARVEIEN 390 AS based?

STOREVARVEIEN 390 AS has its business address in Melsomvik.

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.