BIZTRAC BETA
Retail sale of flowers, plants, seeds and fertilisers

FLORISS HASLESENTERET AS

Org. no. 917782261 Limited company (AS) Sandefjord Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 64,000
Equity NOK 161,000
Incorporated 2016
Employees 8
Share capital NOK 30,000

FLORISS HASLESENTERET AS is registered as a limited company in Sandefjord, Vestfold with organisation number 917782261. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 2016 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Blomsterutsalg med tilhørende aktiviteter samt annen handelsvirksomhet og alt hva dermed står i forbindelse, bl.a deltagelse i andre aksjeselskaper eller virkosmheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 64,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 64,000
Equity
NOK 161,000
Est. value
NOK 328,000

Financial health · 2025

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.5%
Good
Equity as a share of total capital

Who owns FLORISS HASLESENTERET AS?

VIGDIS NORDHAGEN WALNUM
FLORISS HASLESENTERET AS
NOK 3.1m rev. · NOK 64,000 profit

FLORISS HASLESENTERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLORISS HASLESENTERET AS

Who owns FLORISS HASLESENTERET AS?

VIGDIS NORDHAGEN WALNUM is the largest registered owner, with 100.0%.

What is the revenue of FLORISS HASLESENTERET AS?

FLORISS HASLESENTERET AS had revenue of NOK 3.1m in 2025.

Where is FLORISS HASLESENTERET AS based?

FLORISS HASLESENTERET 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.