BIZTRAC BETA
Growing of other non-perennial crops

FIORIBLOMSTER AS

Org. no. 923549269 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −18,000
Equity NOK 131,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

FIORIBLOMSTER AS is registered as a limited company in Asker, Akershus with organisation number 923549269. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av økologiske og spiselige blomster. Produksjon av ettårige hageblomster og grønnsaker for salg samt andre gartner relaterte oppgaver. Kursvirksomhet og foredrag.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −18,000
Equity
NOK 131,000
Est. value
NOK 731,000

Financial health · 2024

Liquidity
1.54
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 FIORIBLOMSTER AS?

AS VESLEMØY
FIORIBLOMSTER AS
NOK 1.2m rev. · NOK −18,000 profit

FIORIBLOMSTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FIORIBLOMSTER AS

Who owns FIORIBLOMSTER AS?

AS VESLEMØY is the largest registered owner, with 100.0%.

What is the revenue of FIORIBLOMSTER AS?

FIORIBLOMSTER AS had revenue of NOK 1.2m in 2024.

Who is the general manager of FIORIBLOMSTER AS?

Ask Vatne Brean is registered as general manager of FIORIBLOMSTER AS.

Where is FIORIBLOMSTER AS based?

FIORIBLOMSTER AS has its business address in Vollen.

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.