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

NARDO BLOMSTER AS

Org. no. 888699872 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 7.1m
Operating profit NOK 1.0m
Equity NOK 977,000
Incorporated 2005
Employees 8
Share capital NOK 30,000

NARDO BLOMSTER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 888699872. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 2005 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og drift av blomsterbutikk og eventuelt investering i aksjer og andre vedripapirer samt aktivitet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.1m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 7.1m
Operating profit
NOK 1.0m
Equity
NOK 977,000
Est. value
NOK 3.8m

Financial health · 2025

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

Who owns NARDO BLOMSTER AS?

MARIA HERMSTAD ALSETH
NARDO BLOMSTER AS
NOK 7.1m rev. · NOK 1.0m profit

NARDO BLOMSTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NARDO BLOMSTER AS

Who owns NARDO BLOMSTER AS?

MARIA HERMSTAD ALSETH is the largest registered owner, with 50.0%.

What is the revenue of NARDO BLOMSTER AS?

NARDO BLOMSTER AS had revenue of NOK 7.1m in 2025.

Who is the general manager of NARDO BLOMSTER AS?

Nina Andreassen is registered as general manager of NARDO BLOMSTER AS.

Where is NARDO BLOMSTER AS based?

NARDO BLOMSTER AS has its business address in Trondheim.

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.