BIZTRAC BETA
Rental and operating of own or leased real estate

BLOMSTERSENTERET VESTFOLD AS

Org. no. 982214580 Limited company (AS) Sandefjord Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 2.2m
Equity NOK 17.8m
Incorporated 2000
Share capital NOK 3.0m

BLOMSTERSENTERET VESTFOLD AS is registered as a limited company in Sandefjord, Vestfold with organisation number 982214580. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 3.0m, divided into 3000 shares. The company's stated purpose is: “Eie og drive fast eiendom og det som derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 2.2m
Equity
NOK 17.8m
Est. value
NOK 16.6m

Financial health · 2025

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

Who owns BLOMSTERSENTERET VESTFOLD AS?

HP EIENDOM HOLDING AS
BLOMSTERSENTERET VESTFOLD AS
NOK 3.6m rev. · NOK 2.2m profit

BLOMSTERSENTERET VESTFOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLOMSTERSENTERET VESTFOLD AS

Who owns BLOMSTERSENTERET VESTFOLD AS?

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

What is the revenue of BLOMSTERSENTERET VESTFOLD AS?

BLOMSTERSENTERET VESTFOLD AS had revenue of NOK 3.6m in 2024.

Who is the general manager of BLOMSTERSENTERET VESTFOLD AS?

Gudmund Baustad is registered as general manager of BLOMSTERSENTERET VESTFOLD AS.

Where is BLOMSTERSENTERET VESTFOLD AS based?

BLOMSTERSENTERET VESTFOLD AS has its business address in Stokke.

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.