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

BLOMSTER & FLORIST AS

Org. no. 821298652 Limited company (AS) Eidsvoll Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 305,000
Equity NOK 400,000
Incorporated 2018
Employees 10
Share capital NOK 30,000

BLOMSTER & FLORIST AS is registered as a limited company in Eidsvoll, Akershus with organisation number 821298652. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 2018 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Butikkhandel med blomster og gaveartikler, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 305,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 305,000
Equity
NOK 400,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns BLOMSTER & FLORIST AS?

ELLEN MARIE ØVERAAS
BLOMSTER & FLORIST AS
NOK 5.3m rev. · NOK 305,000 profit

BLOMSTER & FLORIST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLOMSTER & FLORIST AS

Who owns BLOMSTER & FLORIST AS?

ELLEN MARIE ØVERAAS is the largest registered owner, with 100.0%.

What is the revenue of BLOMSTER & FLORIST AS?

BLOMSTER & FLORIST AS had revenue of NOK 5.3m in 2025.

Who is the general manager of BLOMSTER & FLORIST AS?

Ellen Marie Øveraas is registered as general manager of BLOMSTER & FLORIST AS.

Where is BLOMSTER & FLORIST AS based?

BLOMSTER & FLORIST AS has its business address in Eidsvoll.

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.