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

BLOMSTERPRYD AS

Org. no. 819663122 Limited company (AS) Stjørdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK −39,000
Equity NOK 285,000
Incorporated 2017
Employees 11
Share capital NOK 30,000

Signals

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

BLOMSTERPRYD AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 819663122. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 2017 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive blomsterhandel og virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK −39,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK −39,000
Equity
NOK 285,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns BLOMSTERPRYD AS?

BERIT BEITLAND TOLLEFSEN
BLOMSTERPRYD AS
NOK 2.8m rev. · NOK −39,000 profit

BLOMSTERPRYD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLOMSTERPRYD AS

Who owns BLOMSTERPRYD AS?

BERIT BEITLAND TOLLEFSEN is the largest registered owner, with 100.0%.

What is the revenue of BLOMSTERPRYD AS?

BLOMSTERPRYD AS had revenue of NOK 2.8m in 2024.

Who is the general manager of BLOMSTERPRYD AS?

Berit Beitland Tollefsen is registered as general manager of BLOMSTERPRYD AS.

Where is BLOMSTERPRYD AS based?

BLOMSTERPRYD AS has its business address in Hell.

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.