biztrac. BETA
COMPANY REGISTER PROFILE
982848547 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of flowers, plants, seeds and fertilisers

NESTTUN BLOMSTER AS

Org. no. 982848547 Limited company (AS) Bergen Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 8.9m
Operating profit NOK 167,000
Equity NOK 101,000
Incorporated 2001
Share capital NOK 100,000

NESTTUN BLOMSTER AS is registered as a limited company in Bergen, Vestland with organisation number 982848547. The business is classified under retail sale of flowers, plants, seeds and fertilisers (NACE 47.761). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av blomsterbutikk og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK 167,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.9m
▼ −9 %
Operating profit
NOK 167,000
▼ −45 %
Equity
NOK 101,000
▲ +1 %
Est. value
NOK 860,000

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
6.7%
Satisfactory
Return on total assets
Solidity
4.2%
Weak
Equity as a share of total capital

Who owns NESTTUN BLOMSTER AS?

NESTTUN BLOMSTER AS
NOK 8.9m rev. · NOK 167,000 profit

NESTTUN BLOMSTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESTTUN BLOMSTER AS

Who owns NESTTUN BLOMSTER AS?

BLOMSTERFORUM AS is the largest registered owner, with 100.0%.

What is the revenue of NESTTUN BLOMSTER AS?

NESTTUN BLOMSTER AS had revenue of NOK 8.9m in 2025.

Who is the general manager of NESTTUN BLOMSTER AS?

Lars Jørgen Aadnekvam is registered as general manager of NESTTUN BLOMSTER AS.

Where is NESTTUN BLOMSTER AS based?

NESTTUN BLOMSTER AS has its business address in Nesttun.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.