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

BLOMSTERTORGET AS

Org. no. 961638593 Limited company (AS) Stjørdal Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 5.9m
Operating profit NOK −52,000
Equity NOK 303,000
Incorporated 1991
Employees 17
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−52k kr).

BLOMSTERTORGET AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 961638593. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 1991 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er blomstersalg, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.9m in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.9m
Operating profit
NOK −52,000
Equity
NOK 303,000
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns BLOMSTERTORGET AS?

R. ELI AS
BLOMSTERTORGET AS
NOK 5.9m rev. · NOK −52,000 profit

BLOMSTERTORGET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLOMSTERTORGET AS

Who owns BLOMSTERTORGET AS?

R. ELI AS is the largest registered owner, with 50.0%.

What is the revenue of BLOMSTERTORGET AS?

BLOMSTERTORGET AS had revenue of NOK 5.9m in 2025.

Who is the general manager of BLOMSTERTORGET AS?

Rune Eliassen is registered as general manager of BLOMSTERTORGET AS.

Where is BLOMSTERTORGET AS based?

BLOMSTERTORGET AS has its business address in Stjørdal.

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.