BIZTRAC BETA
Rental and operating of own or leased real estate

STORGATEN 6 SANDEFJORD AS

Org. no. 983805698 Limited company (AS) Sandefjord Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 346,000
Equity NOK 6.2m
Incorporated 2001
Share capital NOK 100,000

STORGATEN 6 SANDEFJORD AS is registered as a limited company in Sandefjord, Vestfold with organisation number 983805698. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Eiendomsdrift og forvaltning, herunder investering i og kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 346,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 346,000
Equity
NOK 6.2m
Est. value
NOK 5.4m

Financial health · 2025

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

Who owns STORGATEN 6 SANDEFJORD AS?

STORGATEN 6 SANDEFJORD AS
STORGATEN 6 SANDEFJORD AS
NOK 3.0m rev. · NOK 346,000 profit

STORGATEN 6 SANDEFJORD AS has 3 registered shareholders:

All shareholders and roles →

Which companies does STORGATEN 6 SANDEFJORD AS own?

STORGATEN 6 SANDEFJORD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STORGATEN 6 SANDEFJORD AS

Who owns STORGATEN 6 SANDEFJORD AS?

STORGATEN 6 SANDEFJORD AS is the largest registered owner, with 46.2%.

What is the revenue of STORGATEN 6 SANDEFJORD AS?

STORGATEN 6 SANDEFJORD AS had revenue of NOK 3.0m in 2025.

Where is STORGATEN 6 SANDEFJORD AS based?

STORGATEN 6 SANDEFJORD AS has its business address in Sandefjord.

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.